Hello !
I'm also looking for a way to achieve something similar but using
attached databases, I mean:
Open a local database that automatically attach other databases and have
views/triggers that use/apply to the attached databases.
Why I want this ?
To overcome sqlite3 limitations with one writer per database and
difficulty to manage multi million records tables spreading then in
individual databases.
Something that the "temp" database can already partially do without
persistence.
Cheers !
On 06/01/17 06:09, Dominique Devienne wrote:
On Thu, Jan 5, 2017 at 11:40 PM, Simon Slavin <slav...@bigfraud.org> wrote:
On 5 Jan 2017, at 7:26pm, Smith, Randall <rsm...@qti.qualcomm.com> wrote:
I'm still trying to figure out a graceful way to implement a "scratch"
database table that has the following properties:
o Can be created on demand while a database connection is open.
o Can include references to other material in the database to
ensure integrity.
o Will be automatically deleted when the database is closed.
It’s not possible to combine the second and third requirements. SQLite is
designed as a multi-process multi-user database.
Not quite though. SQLite does support multi-process multi-user databases of
course,
but one of its primary use case is as an application format too, and often
in that
configuration, there's 1 process and 1 user. Or during an EXCLUSIVE
transaction too.
FWIW. --DD
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
