WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SQLite allows creation of temporary views & triggers that span multiple schema &/or physical database files. This is different to the per-schema (within file) view & trigger
These temporary views & triggers are configured in the on-connect.sql file; however this results in a large cluttered on-connect.sql
Is it possible to add an 'insert or import' type of ability into on-connect.sql to assist in structuring ordered grouping per file of these temporary views & triggers?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
SQLite allows creation of temporary views & triggers that span multiple schema &/or physical database files. This is different to the per-schema (within file) view & trigger
These temporary views & triggers are configured in the
on-connect.sqlfile; however this results in a large clutteredon-connect.sqlIs it possible to add an 'insert or import' type of ability into
on-connect.sqlto assist in structuring ordered grouping per file of these temporary views & triggers?Beta Was this translation helpful? Give feedback.
All reactions