Re: [sqlite] Upgrade from 3.4.2 to 3.5.9 breaks Tcl code

2008-06-12 Thread Jeff Godfrey
D. Richard Hipp wrote: > On Jun 13, 2008, at 12:22 AM, Jeff Godfrey wrote: > >> Thanks for the quick solution. I've adjusted my code accordingly. >> So, >> do you consider this a buglet or more just the closing of a gap that >> shouldn't have existed in the first place? > The column naming

Re: [sqlite] Upgrade from 3.4.2 to 3.5.9 breaks Tcl code

2008-06-12 Thread D. Richard Hipp
On Jun 13, 2008, at 12:22 AM, Jeff Godfrey wrote: >> > Thanks for the quick solution. I've adjusted my code accordingly. > So, > do you consider this a buglet or more just the closing of a gap that > shouldn't have existed in the first place? It's interesting that the > original code works

Re: [sqlite] Upgrade from 3.4.2 to 3.5.9 breaks Tcl code

2008-06-12 Thread Jeff Godfrey
D. Richard Hipp wrote: > On Jun 12, 2008, at 11:08 PM, Jeff Godfrey wrote: > >> dbMem eval {select distinct(owner) from lockinfo order by owner} { >> >> } >> >> That works correctly in my original app using 3.4.2, but complains >> that >> there is no such variable "owner" when using 3.5.9.

Re: [sqlite] Upgrade from 3.4.2 to 3.5.9 breaks Tcl code

2008-06-12 Thread D. Richard Hipp
On Jun 12, 2008, at 11:08 PM, Jeff Godfrey wrote: > > dbMem eval {select distinct(owner) from lockinfo order by owner} { > > } > > That works correctly in my original app using 3.4.2, but complains > that > there is no such variable "owner" when using 3.5.9. Solution 1: dbMem eval

[sqlite] Upgrade from 3.4.2 to 3.5.9 breaks Tcl code

2008-06-12 Thread Jeff Godfrey
Hm... I sent this message last night as a non-list member. I received a notification that it would need to be approved by a moderator before being made public. About 15 hours later, I received a "Post was rejected... No reason given" message. Why's that? So now I'm subscribed again.