Re: [sqlite] Variable substitution (TCL & SQLite)

2008-01-18 Thread Zbigniew Baniewski
On Fri, Jan 18, 2008 at 04:41:12PM +, Simon Davies wrote: > Thus the results are from executing the SQL > SELECT 'column1, column2, column3' FROM some_table; > which I believe tallies with the results you see. Thanks: it's probably the best picture, what is exactly going on there. --

Re: [sqlite] Variable substitution (TCL & SQLite)

2008-01-18 Thread Simon Davies
On 18/01/2008, Zbigniew Baniewski <[EMAIL PROTECTED]> wrote: > ...and now the contents of $columns (SQL variable) in the statement above, > has been replaced with the contents of $columns (TCL variable) - because the > variable names are "compatible". So - that was my assumption - we've got now: >

Re: [sqlite] Variable substitution (TCL & SQLite)

2008-01-18 Thread Zbigniew Baniewski
On Fri, Jan 18, 2008 at 02:54:40PM +0100, Michael Schlenker wrote: > Not really true. > If the part is wrapped in {} then for Tcl the $column is just an ordinary > string with no other meaning than foobar, and NO substitution takes place > before the string is passed to SQLite. Yes, as I wrote

Re: [sqlite] Variable substitution (TCL & SQLite)

2008-01-18 Thread Michael Schlenker
Zbigniew Baniewski schrieb: On Fri, Jan 18, 2008 at 02:54:40PM +0100, Michael Schlenker wrote: $name is an application variable if it appears in a place where an application variable is valid. [..] Your usage fails, because the select list is no valid place to use application variables, so

Re: [sqlite] Variable substitution (TCL & SQLite)

2008-01-18 Thread Michael Schlenker
Zbigniew Baniewski schrieb: On Thu, Jan 17, 2008 at 11:13:59PM -0500, D. Richard Hipp wrote: The rules of TCL parsing are that text within {...} gets passed into its command exactly as written with the outermost {...} removed. [..] In other words, the $columns was *not* expanded by TCL. It

Re: [sqlite] Variable substitution (TCL & SQLite)

2008-01-18 Thread Zbigniew Baniewski
On Thu, Jan 17, 2008 at 11:13:59PM -0500, D. Richard Hipp wrote: > The rules of TCL parsing are that text within {...} gets passed into > its command exactly as written with the outermost {...} removed. [..] > In other words, the $columns was *not* expanded by TCL. It got > passed down into

Re: [sqlite] Variable substitution (TCL & SQLite)

2008-01-17 Thread D. Richard Hipp
On Jan 17, 2008, at 10:23 PM, Zbigniew Baniewski wrote: I'm choosing desired column names dynamically, then store all the names in one variable, something like this... set columns "column1, column2, column3" The names are chosen in much more complicated way, but the above is just a

[sqlite] Variable substitution (TCL & SQLite)

2008-01-17 Thread Zbigniew Baniewski
I'm choosing desired column names dynamically, then store all the names in one variable, something like this... set columns "column1, column2, column3" The names are chosen in much more complicated way, but the above is just a variable contents example. I'm trying then to fetch the data like