Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f63EgNa01428; Tue, 3 Jul 2001 10:42:23 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f63EfxJ18357; Tue, 3 Jul 2001 10:41:59 -0400 (EDT) To: David Stanaway cc: pgsql-sql@postgresql.org, pgsql-interfaces@postgresql.org Subject: Re: [SQL] indexing arrays in pgaccess's query interface is failing In-reply-to: References: Comments: In-reply-to David Stanaway message dated "Tue, 03 Jul 2001 19:05:05 +1000" Date: Tue, 03 Jul 2001 10:41:59 -0400 Message-ID: <18354.994171319@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200107/12 X-Sequence-Number: 1765 [ redirected to pgsql-interfaces, which seems a more appropriate venue ] David Stanaway writes: > --.. And now the query that I am having problems with. > > SELECT itID, itProperties[akID], akName > FROM items, arraykeys; > > In pgaccess, > when I try to execute the same query in query builder, > I get the tcl error dialogue: > Error: invalid command name "akID" Someone isn't quoting the query string correctly on the Tcl side --- [akID] is Tclese for command substitution. Sounds like pgaccess expects the user to quote command punctuation characters that should be passed through. Not sure if that should be regarded as a bug or a feature. It could be considered a feature that you can enter SQL commands with Tcl command substitution performed on them, but it's something that would confuse non-Tcl-users a lot. regards, tom lane