2 ms·
Another problem is explained in the feature request that another commenter linked to: https://code.google.com/p/android/issues/detail?id=202658 https://code.goo
by iainmerrick 10y ago
Another problem is explained in the feature request that another commenter linked to: https://code.google.com/p/android/issues/detail?id=202658 https://code.google.com/p/android/issues/detail?id=202658
You have no idea what version of sqlite the OS might be using, so you can't rely on consistent behavior. In many cases the vendor will have tinkered with it and messed it up. Comprehensively testing on all Android devices is basically impossible because there are so many models out there.
- Zigurd 10y agoThat sounds like an argument against direct access to sqlite.so.
- iainmerrick 10y agoHmm, yeah, but only partly-- The reason they can tinker with it is that it's not public; if it were public it would (hopefully) be better-defined, locked down and stable, part of the Android compatibility test suite. That feature request would let people supply their own sqlite.so, and also redirect the Java API to use it. Seems like a very promising approach.