Re: [sqlite] Tcl bindings are a little problematic.

2010-09-07 Thread Paweł Salawa
Hi, I have a feeling that thread "Tcl bindings are a little problematic." is forgotten, but yet not concluded. I want to catch your eye again on it. Please see response below. Regards, Pawel From: Paweł Salawa Subject: Re: Tcl bindings are a little problematic. Newsgroups: gmane.comp.db.sql

Re: [sqlite] Tcl bindings are a little problematic.

2010-09-05 Thread Paweł Salawa
> The column names on queries that do not have AS clauses on the columns are > undefined and are subject to change. To get specific column names, use AS: > > select a1.txt AS a1, a2.txt AS a2 > > Then your arr() will contain entries a(*), a(a1), and a(a2). True, but in case of custom S

Re: [sqlite] Tcl bindings are a little problematic.

2010-09-02 Thread Richard Hipp
On Wed, Sep 1, 2010 at 6:11 PM, Paweł Salawa wrote: > Hi, > > It's pretty hard to make a SELECT from same table, but using two different > aliases for the table and at the same time also getting column names in > results - using Tcl bindings. > > The SQL query would be: > > select a1.txt, a2.txt

[sqlite] Tcl bindings are a little problematic.

2010-09-02 Thread Paweł Salawa
Hi, It's pretty hard to make a SELECT from same table, but using two different aliases for the table and at the same time also getting column names in results - using Tcl bindings. The SQL query would be: select a1.txt, a2.txt from a a1 join a a2 using (ref) where a1.lang = 'fre