Re: [sqlite] What is wrong with this update SQL

2012-11-23 Thread Pat .
Simon, I liked your method of attack with the 2 tables. :) On Nov 22, 2012 6:59 AM, "Simon Slavin" wrote: > > On 22 Nov 2012, at 10:47am, Bart Smissaert > wrote: > > > Ignore this e-mail, it was a simple mistake from my side and nil to do > > with SQLite. > > It takes a big man to admit a mistak

Re: [sqlite] Status analyze with Sqlite

2012-11-23 Thread Keith Medcalf
Your expected result does not make any logical algorithmic sense whatsoever. --- () ascii ribbon campaign against html e-mail /\ www.asciiribbon.org > -Original Message- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- > boun...@sqlite.org] On Behalf Of Steffen Mangold > S

[sqlite] Matchinfo slows down query

2012-11-23 Thread Joost Voogt
Hi, I'm currently working on a project that makes use of the SQLite FTS functionality (version 3.7.14) on a large data set of POI (point of interest). Most of the time it works fine but I stumbled on a few queries that take a lot of time to complete. It's confusing to me what actually is going on

Re: [sqlite] Status analyze with Sqlite

2012-11-23 Thread Simon Slavin
On 23 Nov 2012, at 9:01am, Steffen Mangold wrote: > But it should be: > ID| Begin | End | Status > --- > 0 | 2012-07-24 22:23:00 | 2012-07-24 22:23:05 | status1 > 0 | 201

Re: [sqlite] Status analyze with Sqlite

2012-11-23 Thread Clemens Ladisch
Steffen Mangold wrote: > TimeStamp | Status > - > 2012-07-24 22:23:00 | status1 > 2012-07-24 22:23:05 | status1 > 2012-07-24 22:23:10 | status2 > 2012-07-24 22:23:16 | status2 > 2012-07-24 22:23:21 | status1 > 2012-07-24 22:23:26

Re: [sqlite] Status analyze with Sqlite

2012-11-23 Thread Steffen Mangold
Hi Clemens, first thank you for your comments. > > It works for what you've asked. Perhaps you should not have kept your actual > requirements a secret. > Sorry for being unclear! :( Hope my English is understandable (I'm from Germany). > > So you want to group only consecutive events with id

Re: [sqlite] Status analyze with Sqlite

2012-11-23 Thread Clemens Ladisch
Steffen Mangold wrote: > this won't work It works for what you've asked. Perhaps you should not have kept your actual requirements a secret. > if the table look like this: > > ID | TimeStamp | Status > > 0| 2012-07-24 22:2

Re: [sqlite] What is wrong with this update SQL

2012-11-23 Thread Bart Smissaert
Did a bit of further testing and when the age field is an integer field and the band field is another field with text datatype then the method with a lookup table is slightly faster. Either way there isn't much in it. RBS On 11/22/12, Simon Slavin wrote: > > On 22 Nov 2012, at 5:53pm, Bart Smiss

Re: [sqlite] Status analyze with Sqlite

2012-11-23 Thread Steffen Mangold
> ID| TimeStamp | Status > > 0 | 2012-07-24 22:23:00 | status1 > 1 | 2012-07-24 22:23:05 | status1 > 2 | 2012-07-24 22:23:10 | status2 > 3 | 2012-07-24 22:23:16 | status2 > 4 | 2012-07-24 22:23:21 |