I have written a quick and dirty test program (see below) and tested
it using different build options against 4 different emulator
versions.
The tests were repeated building different build options of the same
program:
build 1
android:minSdkVersion="3"
android:targetSdkVersion="4"
build target 4
build 2
android:minSdkVersion="3"
android:targetSdkVersion="4"
build target 8
build 3
android:minSdkVersion="3"
android:targetSdkVersion="8"
build target 8
All 3 build of the test program returned the same result on each
platform
Emulator running 1.5 returned 3.5.9 for every build
Emulator running 1.6 returned 3.5.9 for every build
Emulator running 2.1 returned 3.5.9 for every build
Emulator running 2.2 returned 3.6.22 for every build
Source code (quick and dirty) will clean up later:
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.device_info);
final String databaseName = ":memory:";
final String query = "SELECT sqlite_version() AS sqlite_version";
SQLiteDatabase db =
SQLiteDatabase.openOrCreateDatabase(databaseName, null);
Cursor cursor = db.rawQuery(query, null);
String report = "Querying SQLite for it's version using\n" + query
+"\nreturned\n\n";
while (cursor.moveToNext())
{
report += cursor.getString(0) + "\n";
}
final TextView reportTextView =
(TextView)findViewById(R.id.ReportTextView);
reportTextView.setText(report);
}
On Jul 11, 1:32 pm, RichardC <[email protected]> wrote:
> Think I have found one ... will upload a test app (if it works) later
> this afternoon and post here when it is available.
>
> --
> Richard
>
> On Jul 11, 9:21 am, Mark Carter <[email protected]> wrote:
>
> > Is there any way to (programmatically) check what version of SQLite is
> > installed?
>
> > On Jun 24, 1:09 pm, Mark Carter <[email protected]> wrote:
>
> > > Hmmm - this is a bit worrying, isn't it? How to possibly test SQL which
> > > can
> > > potentially run so differently on different devices?
>
> > > One starting point would be get a list of SQLite version numbers on each
> > > device available...
>
> > > 2010/6/24 Tomáš Hubálek <[email protected]>
>
> > > > SQL Lite is definitely simpler but in Oracle it sometimes happens that
> > > > the
> > > > same SQL has very different performance on different versions because of
> > > > different explain plan.
>
> > > > Tom
>
> > > > On Thu, Jun 24, 2010 at 12:48 PM, Mark Carter
> > > > <[email protected]>wrote:
>
> > > >> True - though the SQL is a little complex and I'd like to simplify it
> > > >> before posting.
>
> > > >> However, whatever the SQL is, there has to be an explanation for the
> > > >> different outcome.
>
> > > >> 2010/6/24 Tomáš Hubálek <[email protected]>
>
> > > >> Maybe full SQL would give more clue...
>
> > > >>> Tom
>
> > > >>> On 24 čvn, 10:13, Mark Carter <[email protected]> wrote:
> > > >>> > Same data, same code, but different results on these two devices.
>
> > > >>> > On the Nexus One, the (INNER JOIN) query runs (first call to
> > > >>> > Cursor.moveToNext()) after a fraction of a second but on the Hero it
> > > >>> > just hangs.
>
> > > >>> > I haven't been able to reduce the scenario to something simple yet,
> > > >>> > but it seems to involve using OR within an ON clause.
>
> > > >>> > Anyone know why there might be a difference on these two devices?
>
> > > >>> --
> > > >>> 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]<android-developers%2Bunsubs
> > > >>> [email protected]>
> > > >>> For more options, visit this group at
> > > >>>http://groups.google.com/group/android-developers?hl=en
>
> > > >> --
> > > >> 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]<android-developers%2Bunsubs
> > > >> [email protected]>
> > > >> For more options, visit this group at
> > > >>http://groups.google.com/group/android-developers?hl=en
>
> > > > --
>
> > > > ---------------------------------------------------------------------------
> > > > --------------------
> > > > Tom Hubalek ([email protected]),
> > > >http://android.hubalek.net,http://blog.hubalek.net/
> > > >http://facebook.com/thubalek,http://www.linkedin.com/in/thubalek
> > > >http://twitter.com/thubalek,http://twitter.com/android_dev_tom
>
> > > > --
> > > > 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]<android-developers%2Bunsubs
> > > > [email protected]>
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/android-developers?hl=en
--
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
