On Jan 18, 1:49 am, kristianlm wrote:
> 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:
>
> htt
On Jan 12, 1:53 pm, jotobjects wrote:
> On Jan 11, 9:14 pm, Elliott Hughes wrote:
>
> > On Dec 19 2009, 2:05 am, kristianlm 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 n
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 wrote:
> On Jan 12, 1:53 pm, jotobjects wrote:
>
>
>
> > On Jan 11, 9:14 pm, Elliott Hughes wrote:
>
> > > On Dec 19 2009, 2:05 am, kr
There is JDBC support in Android (see online reference for package
java.sql). There is also a built-in, though somewhat limited JDBC
driver for SQLite. Try this inside an Activity:
try {
String db = "jdbc:sqlite:" + getFilesDir() + "/test.db";
Class.forName("SQLite
Hi Mark,
and thanks for your feedback.
I cannot say I quite follow you though. There isn't really that much
overhead involved, and my JAR-file is only 17kB. The JDBC Driver is a
simple wrapper for the SQLiteDatabase calls, but only a small subset
of the JDBC interface is implemented.
I haven't us
> JDBC is designed to be used on devices with lots of RAM, lots of CPU
> speed, comparatively unlimited storage space for application code,
> full-time AC power, to connect to local databases and database servers.
>
JDBC drivers are often/usually used with remote databases (this is the
simplest me
Hi Joerg,
sorry your post just came in while I was writing the other.
I cant believe this though - there's already a driver available? I
can't find that in the docs anywhere! Which java.sql online manual are
you looking at? I'm at
http://developer.android.com/reference/java/sql/package-summary
no worries! I think we're all confused here (except Joerg)
i'm glad I'm not the only one who got this JDBC-android-support jungle
wrong
On Dec 8, 7:46 pm, "Mark Murphy" wrote:
> > There is JDBC support in Android (see online reference for package
> > java.sql). There is also a built-in, though so
On Dec 8, 11:02 am, kristianlm wrote:
> I cant believe this though - there's already a driver available? I
> can't find that in the docs anywhere! Which java.sql online manual are
> you looking at? I'm
> athttp://developer.android.com/reference/java/sql/package-summary.html
http://dev.android
I see. I still think the documents are lacking!
Am I the only one who'd want a comment on the JDBC
support in the dev-guide documents?
There seems to be a fair share of confused people out there ...
On Dec 8, 8:33 pm, jotobjects wrote:
> On Dec 8, 11:02 am, kristianlm wrote:
>
> > I cant beli
I agree the existence of the driver should be mentioned at least in
the JDBC package docs. Would you mind creating a ticket for this?
JDBC is somewhat of a second-class citizen in the Android world, since
Android has its own database API (that is actually not too far away
from JDBC, but has much b
Ok. Thanks a lot Joerg!
I wanna create a ticket, but I don't know where to turn
Is this where I'm supposed to post:
http://code.google.com/p/android/issues/list
It seems to be only for bugs though, is it?
Anyhow, I commited a bug there half a year
ago and it still hasn't been looked at, is
anyon
Hi Kris,
yes, this is the general bugtracker for the Android open-source
project. Please use it. I think it is adequate also for documentation
issues or feature requests. I don't know about your specific issue,
but the issues are being looked at by the Android team (mostly Google
guys) and worked
On Dec 8, 10:41 pm, Joerg Pleumann 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 pleas
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 wrote:
> On Dec 8, 10:41 pm, Joerg Pleumann wrote:>
> Regarding androi
JDBC drivers are never used directly by JDBC applications. In a JDBC
application you reference the URI name of the driver in
DriverManager.getConnection(). That is the only time you ever see the
driver and you never actually call a method on the driver itself in a
JDBC application. This has nothi
Hi again everybody.
I really wanna get to the bottom of this.
I posted a ticket
http://code.google.com/p/android/issues/detail?id=5437
and, perhaps as expected, the reply sounded:
"this code is undocumented because
it's unsupported. please do not use
undocumented API."
The ticket has been cl
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 wrote:
> Hi jotobject,
> I don't understant why this wouldn't be part of the public API. if
> Android is shipped with a JDBC dr
On Dec 15, 8:46 am, kristianlm wrote:
> I understand that the driver doesn't have to be
> documented if you're not supposed to be using
> it since it's going "low-level".
That's right. There is nothing useful you can do with the driver
anyway. That's what the JDBC API is for.
>
> But the dri
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? without
loading the jdbc driver with Class.forName() it isn't registered.
that concludes the code snippet in Joerg's post above is
not allowed?
On Dec 19, 2:05 am, kristianlm wrote:
> hi Elliott,
>
> what exactly does it mean that the driver is unsupported and that
> it shouldn't be used?
The SQLite driver could change in a future a release. It is
undocumented because you should not rely on the API for the driver.
That means you shoul
On Dec 22 2009, 12:50 pm, jotobjects wrote:
> On Dec 19, 2:05 am, kristianlm wrote:
>
> > hi Elliott,
>
> > what exactly does it mean that the driver is unsupported and that
> > it shouldn't be used?
>
> The SQLite driver could change in a future a release. It is
> undocumented because you sho
On Dec 19 2009, 2:05 am, kristianlm 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 A
On Jan 11, 9:14 pm, Elliott Hughes wrote:
> On Dec 19 2009, 2:05 am, kristianlm 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'
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 sim
You can just include the Android driver in your application if you
want to be sure that it is available on every device. You can find
the Android SQLLite driver at this location -
http://android.git.kernel.org/?p=platform/dalvik.git;a=blob;f=libcore/sql/src/main/java/SQLite/JDBCDriver.java;h=63b9
> There is JDBC support in Android (see online reference for package
> java.sql). There is also a built-in, though somewhat limited JDBC
> driver for SQLite.
:: blink, blink ::
My apologies!
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App Developer Books: http://commonsware.co
27 matches
Mail list logo
