In some cases, it's convenient to use one database file per table, as in current implementation.
But a typical SQLite application would open one database file, and create multiple tables in it.
Such behavior is not currently possible, but could be easily added, since it is possible to pass options to Lawnchair constructor and these options are then forwarded to the adapter. There could be an option called db or database that would be used to set name for database file.
Is there any reason for creating database files one per table?
In some cases, it's convenient to use one database file per table, as in current implementation.
But a typical SQLite application would open one database file, and create multiple tables in it.
Such behavior is not currently possible, but could be easily added, since it is possible to pass options to Lawnchair constructor and these options are then forwarded to the adapter. There could be an option called
db
ordatabase
that would be used to set name for database file.Is there any reason for creating database files one per table?
If not, I will send you a pull request.