Re: [sqlite] Instead of triggers

2012-12-27 Thread BareFeetWare
On 27/12/2012, at 11:49 PM, Alem Biscan wrote: > So user decides to modify a record. He changes *primary, field2, > field3*values trough textboxes, and the app sends parametarised update > query to > sqlite engine. > > UPDATE MYVIEW > SET *primary = @a*, >*field2= @b*. >

Re: [sqlite] Instead of triggers

2012-12-27 Thread Hick Gunter
Biscan [mailto:biscana...@gmail.com] Gesendet: Donnerstag, 27. Dezember 2012 13:50 An: General Discussion of SQLite Database Betreff: [sqlite] Instead of triggers Hello community, I am a little bit confused by instead of update trigger logic. Lets say there is a trigger MYTRIGGER which is an INSTEAD

Re: [sqlite] Instead of triggers

2012-12-27 Thread Igor Tandetnik
Alem Biscan wrote: > I am a little bit confused by instead of update trigger logic. > > Lets say there is a trigger MYTRIGGER which is an INSTEAD OF UPDATE trigger > that belongs to view named MYVIEW. > MYTRIGGER should update table MYTABLE with values sent from an application. > > UPDATE MYTABL

[sqlite] Instead of triggers

2012-12-27 Thread Alem Biscan
Hello community, I am a little bit confused by instead of update trigger logic. Lets say there is a trigger MYTRIGGER which is an INSTEAD OF UPDATE trigger that belongs to view named MYVIEW. MYTRIGGER should update table MYTABLE with values sent from an application. UPDATE MYTABLE SET *p