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
It's quite common to create some kind of large database table or constellation
of tables that will be used for intermediate work product, and which will be
deleted when an operation, or the database session, is complete. This kind of
thing is an obvious candidate for TEMPORARY tables in
This question may be off-topic for this list, since it deals with using SQLite
in a specific setting rather than SQLite itself. Apologies if so. Thanks very
much if anyone can provide any insight.
I am one of the hapless souls who need access to SQLite's CTE capabilities
(introduced in
Hi.
I'm creating a specialized index table to a persistent table that I need to
speed up a one-time operation. This seems like a great application for a
TEMPORARY table in SQLite, so the index will always be reliably cleaned up.
However, I can't find a way to have REFERENCES to the main table
Thanks for the ideas, Simon. Already good on the general principles. The
approach of just periodically deleting all the indices and starting over from
scratch with a massive, comprehensive re-profiling effort might work on a small
project, an overstaffed one, one that doesn't change much, or
I'm developing a medium-sized SQLite-based app (maybe 50 tables, 400 query,
insert, and update routines). As we all know, having the right set of table
indices is vital for getting decent performance from SQL. However, I'm getting
to the point on this project where this is getting to be very
6 matches
Mail list logo
