There are a number of open source JDBC drivers for SQLLite out there already (including the one already built into Android).
On Jan 21, 10:22 pm, Elliott Hughes <e...@google.com> wrote: > On Jan 12, 1:53 pm, jotobjects <jotobje...@gmail.com> wrote: > > > > > On Jan 11, 9:14 pm, Elliott Hughes <e...@jessies.org> wrote: > > > > On Dec 19 2009, 2:05 am, kristianlm <kristianl...@gmail.com> wrote: > > > > > hi Elliott, > > > > > what exactly does it mean that the driver is unsupported and that > > > > it shouldn't be used? > > > > > are you saying that JDBC should not be used at all? > > > > you can use JDBC, though it isn't well tested. but we do publicly > > > support the java.sql API. > > > Hi Elliott - > > > You cannot use JDBC if you can't get a Connection. And you cannot get > > a Connection unless there is some documented way for the DriverManager > > to find the SQLite driver. ASFAIK this would be done by the platform > > registering the driver, or it is done in a static initializer in the > > driver class, hence the use of Class.forName(). > > > This is the pattern that you apparently say is NOT supported - > > > String db = "jdbc:sqlite:" + getFilesDir() + "/test.db"; > > Class.forName("SQLite.JDBCDriver"); > > Connection conn = DriverManager.getConnection(db); > > > So then what is the correct supported way to get a Connection object? > > you supply your own driver, and use that. > > --elliott > > > If there is no documented way then maybe it is true that JDBC is NOT > > usable on Android currently? > > > I don't think JDBC is that critical to the platform but it would be > > nice to clarify if it is even usable. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en