[sqlite] caveat on blanket UPDATE triggers

2011-07-14 Thread Ben Harper
This may be specific to RTree indexes - I haven't taken the time to fully understand it. Dangerous: CREATE TRIGGER ON UPDATE ON tablename { SET RTREE MIN/MAX } Fine: CREATE TRIGGER ON UPDATE OF geometry OF tablename { SET RTREE MIN/MAX } Failure to specify the field name explicitly results in a

Re: [sqlite] caveat on blanket UPDATE triggers

2011-07-14 Thread Dan Kennedy
On 07/14/2011 10:42 PM, Ben Harper wrote: > This may be specific to RTree indexes - I haven't taken the time to fully > understand it. > > Dangerous: > CREATE TRIGGER ON UPDATE ON tablename { SET RTREE MIN/MAX } > > Fine: > CREATE TRIGGER ON UPDATE OF geometry OF tablename { SET RTREE MIN/MAX } >

Re: [sqlite] caveat on blanket UPDATE triggers

2011-07-14 Thread Ben Harper
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Dan Kennedy [danielk1...@gmail.com] Sent: 14 July 2011 06:02 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] caveat on blanket UPDATE triggers On 07/14/2011 10:42 PM, Ben Harper wrote

Re: [sqlite] caveat on blanket UPDATE triggers

2011-07-14 Thread Simon Slavin
On 14 Jul 2011, at 9:28pm, Ben Harper wrote: > My mistake. The UPDATE trigger can be catch-all-fields (ie no fields > specified), > and it is still correct. If that is meant to be a normal TRIGGER than you are using curly brackets incorrectly. The syntax does not involve brackets. See http: