SQLite3 has become very powerful over the years due to its relative simplicity, single-file database, and immediacy. I believe the number of people (including programmers) who use SQLite3 as a stand-alone database tool is vastly underestimated. From those, only the client-server over network speedup is irrelevant to SQLite3. There are several advantages to using stored procedures. This argument applies equally well to all database engines. Stored procedures aren't really needed for Sqlite, since the program you write around Sqlite can certainly implement any 'stored' procedures itself. Par5 blob, par6 blob, par7 blob, par8 blob, par9 blob ) ĬREATE TRIGGER Fakt after UPDATE OF job ON stackįOR EACH ROW WHEN new.job='Fakt' and argc()>=1 Par0 blob, par1 blob, par2 blob, par3 blob, par4 blob, Level integer, inserted float, returned float, - some debug support
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |