On Thu, Jan 24, 2008 at 10:59:17AM -0500, Samuel R. Neff wrote: > Due to the restriction that triggers cannot span databases, I have my main > data tables, history tables, and the ActiveTransaction table all in the same > database. I'd really rather the history tables be in a separate database > because they can grow quite large and when I ask a customer to e-mail me > their database, I'd like them to be able to easily e-mail the main data only > without the extra history info.
You could always copy the users_history table records to an attached DB and "delete from users_history;" after every, or every N, transactions on your main DB. This ways your users_history table size is bounded in the main DB and you still get to keep all your history in a separate DB. Triggers across DBs could only work if there was a way to create a persistent DB ATTACHment -- a way to tell SQLite to ATTACH dependencies of such triggers whenever you open the DB. I imagine that wouldn't be too hard, but I'm not writing nor maintaining the code. Nico -- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
