On Thu, 5 Jan 2017 19:26:26 +0000 "Smith, Randall" <rsm...@qti.qualcomm.com> wrote:
> * Can be created on demand while a database connection is open. > * Can include references to other material in the database to > ensure integrity. > * Will be automatically deleted when the database is closed. There is a conventional approach that would work just as well. Instead of creating and dropping the table per session, create it once as part of the schema. Obviously, you can set up foreign key constraints for it. Per session, delete all rows at the beginning. If multiple users are involved, make the user id part of the key, and delete all rows per user. If you want to, delete all rows before exiting, too. But that's optional; no one can see rows in a database that's not open. It may help to remember that relational theory doesn't include any notion of "connection" to the database. There are tables and they have rows. Operations on those tables affect the rows. Creating the tables, per se, is outside the theory, as too is the idea of creating them automatically at time of connection. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
