Hi folks, I guess we've concluded that the built-in JDBC for Android should not be used (even though it's there). Those of you who still want to use JDBC on Android can check out the JDBC driver I started myself for precisely this reason:
http://code.google.com/p/sqldroid/ It's a relatively simple implementation but does its job: offer jdbc access to android sqlite db. And thanks for all the constructive feedback! Kris On Jan 12, 10:53 pm, jotobjects <[email protected]> wrote: > On Jan 11, 9:14 pm, Elliott Hughes <[email protected]> wrote: > > > On Dec 19 2009, 2:05 am, kristianlm <[email protected]> wrote: > > > > hi Elliott, > > > > what exactly does it mean that the driver is unsupported and that > > > it shouldn't be used? > > > > areyousaying thatJDBCshould not be used at all? > > >youcanuseJDBC,thoughitisn'twelltested.butwedopublicly > >supportthejava.sqlAPI. > > Hi Elliott - > > YoucannotuseJDBCifyoucan't get a Connection. Andyoucannot 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 theuseof Class.forName(). > > This is the pattern thatyouapparently 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? > If there is no documented way then maybe it is true thatJDBCis NOT > usable on Android currently? > > I don't thinkJDBCis that critical to the platformbutit 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
