the JDBC driver is undocumented because it's unsupported. please do
not use reflection to access undocumented/unsupported API.
--elliott
On Dec 14, 5:29 am, kristianlm <kristianl...@gmail.com> wrote:
> Hi jotobject,
> I don't understant why this wouldn't be part of the public API. if
> Android is shipped with a JDBC driver, why not let people use it? It's
> certainly useful for many of us!
>
> Kris
>
> On Dec 12, 10:42 pm, jotobjects <jotobje...@gmail.com> wrote:
>
> > On Dec 8, 10:41 pm, Joerg Pleumann <joerg.pleum...@gmail.com> wrote:>
> > Regarding android.jar, I never checked but I could imagine that it
> > > contains only the public API classes and might even have the actual
> > > bytecode erased. Nothing is ever run against it. It is just there to
> > > make Javac or Eclipse happy (somebody please correct me if I'm wrong).
> > > On the device, the driver should be part of /system/framework/
> > > core.jar.
>
> > The SQLite driver is never used by the public API. You pass the name
> > as a String URI "jdbc:sqlite:" to getConnection(). That is the way
> > JDBC always works. The drivers are not part of the public API so the
> > documentation is NOT missing anything regarding drivers.
>
> > As far as I can see the only missing documentation is the URI
> > "jdbc:sqlite:" as in Joerg's example -
>
> > String db = "jdbc:sqlite:" + getFilesDir() + "/test.db";
> > Class.forName("SQLite.JDBCDriver");
> > Connection conn = DriverManager.getConnection(db);
>
> > The Class.forName() call is only necessary if Android does not
> > automatically register the driver with DriverManager (I don't know if
> > it does or not).
--
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
