On Mon, Jun 26, 2017 at 4:28 AM, Martin Desruisseaux <[email protected]> wrote: > It seems similar to instantiating a javax.sql.DataSource subtype in > standard Java. But javax.naming purpose is (among others) to enable this > operation outside Java code, for example in a web application > configuration file, in some central registry managed by a container, > etc. But maybe this is considered not necessary on Android. For example > can we assume that the embedded SQLite server is always running and that > most users are unlikely to want to use another database engine?
Yes that's right, SQLite is always available and it is the preferred method of using databases in Android. So it is not necessary to use another database engine. -- Sisinda
