Re: [sqlite] Trigger behaviour on UPDATE after release 3.24.0

2018-06-07 Thread Rowan Worth
On 6 June 2018 at 07:14, Richard Hipp wrote: > On 6/5/18, Stéphane Aulery wrote: > > Hello, > > > > The changelog of the last release [1] say at the point 13 : > > > > UPDATE avoids writing database pages that do not actually change. For > > example, "UPDATE t1 SET x=25 WHERE y=?" becomes a

Re: [sqlite] Trigger behaviour on UPDATE after release 3.24.0

2018-06-05 Thread Richard Hipp
On 6/5/18, Stéphane Aulery wrote: > Hello, > > The changelog of the last release [1] say at the point 13 : > > UPDATE avoids writing database pages that do not actually change. For > example, "UPDATE t1 SET x=25 WHERE y=?" becomes a no-op if the value in > column x is already 25. Similarly, when

[sqlite] Trigger behaviour on UPDATE after release 3.24.0

2018-06-05 Thread Stéphane Aulery
Hello, The changelog of the last release [1] say at the point 13 : UPDATE avoids writing database pages that do not actually change. For example, "UPDATE t1 SET x=25 WHERE y=?" becomes a no-op if the value in column x is already 25. Similarly, when doing UPDATE on records that span multiple