On Mon, 20 Oct 2008 12:38:29 +0200, jm cuaz <[EMAIL PROTECTED]> wrote in General Discussion of SQLite Database <sqlite-users@sqlite.org>:
>Hello, > >We try to port an application specialised in financial calculus written >in VBA + MS Access toward Tcl + Sqlite. > >In this application, 90% of the calculus is directly processed at the >SQL level via INSERT/UPDATE statements executed against the db, and >subsets are calculated with INNER JOINS between the tables inside each >statement. >In consequence, our statements are easily dealing with 3/4 tables (not >rarely more) at once. > >But in this purpose, we encounter a severe issue in the fact that in >Sqlite, UPDATE statements, in the contrary of INSERT statements, >doesn't compute several tables at once. > >On this mailing list, Igor Tandetnik (thank's Igor) showed us a >workaround via subqueries inserted in the FROM and WHERE clauses of >UPDATE statements. > >But, while not impossible, it is difficult to do so when the number of >tables involved is greater than 3. > >Ticket 3222 had still made a request in this direction. > >Does anybody kows if there is any plan for enhancing Sqlite's UPDATE >statement in this direction ? > >Thank's > >Jean-Marie There might be a workaround: Create an updateble view and UPDATE that view. An updateble view is a view plus an INSTEAD OF trigger. http://www.sqlite.org/lang_createtrigger.html#instead_of_trigger -- ( Kees Nuyt ) c[_] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
