Re: [sqlite] update on Ticket 3437

2010-01-24 Thread ve3meo
You're right! I arrived at a failure of a different kind because I did not drop the Races table as per his script between adding the first record with ID='20' and the second with ID=20. If Races table contains two records, the first with ID='20' and the second with ID=20, his query fails, even t

Re: [sqlite] update on Ticket 3437

2010-01-24 Thread Jean-Christophe Deschamps
>No, it fails because 20 != '20' And also possibly because Date LIKE "2009%" should be Date LIKE '2009%' everywhere it appears. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlit

Re: [sqlite] update on Ticket 3437

2010-01-24 Thread Igor Tandetnik
Tom Holden wrote: > Nick, I think your query fails because there is a potential for multiple > values on the right-hand side of WHERE RaceID=. No, it fails because 20 != '20' Igor Tandetnik ___ sqlite-users mailing list sqlite-users@sqlite.org http://s

Re: [sqlite] update on Ticket 3437

2010-01-24 Thread Tom Holden
ery be better composed as: SELECT * from races, times WHERE RACEID = ID and Races.Name = 'totley moor' AND Date LIKE "2009%"; Tom - Original Message - From: To: Sent: Saturday, January 23, 2010 7:59 PM Subject: [sqlite] update on Ticket 3437 > Hi, > I submitte

[sqlite] update on Ticket 3437

2010-01-24 Thread nick
Hi, I submitted this some time ago, see http://www.sqlite.org/cvstrac/tktview?tn=3437,39. I've just been messing about with this again and have found out what was happening. The following script demonstrates the problem and resolution: [begin bug2.sql] /* this command line will demonstrate