Column qualifier issue

[Jim Wilson]

As far as I can tell, there isn't a way to get postgresql to accept column
qualifiers (e.g. tablenames). A 'parse error at or near "."' gets returned.

I'm using a closed source application that has successfully handled a number
of other sql92 compatible datasources via odbc. The problem is the app
insists on qualifying column names all the time, even in Insert and Update
statements. That is not incorrect according to sql92, even though one could
assume that a qualifier is never required with update and insert.

Is it possible to get Postgres to accept these statements? Anyone have a hack
to let this stuff through the parser?

Tia,

Jim
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Tom Lane]

"Jim Wilson" <ji**@kelcomaine.com> writes:

As far as I can tell, there isn't a way to get postgresql to accept column
qualifiers (e.g. tablenames). A 'parse error at or near "."' gets returned.

You're either very confused or using a *very* old version of Postgres.

What version is it, what query are you issuing exactly, and what exactly
is the error message? (Cut-and-paste from a psql session would be the
best way to answer the last two ... or if the query is being issued from
another application, you could turn on query logging and send in an
excerpt from the postmaster log.)

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

[Stephan Szabo]

On Mon, 12 Jan 2004, Tom Lane wrote:

"Jim Wilson" <ji**@kelcomaine.com> writes:

As far as I can tell, there isn't a way to get postgresql to accept column
qualifiers (e.g. tablenames). A 'parse error at or near "."' gets returned.

You're either very confused or using a *very* old version of Postgres.

What version is it, what query are you issuing exactly, and what exactly
is the error message? (Cut-and-paste from a psql session would be the
best way to answer the last two ... or if the query is being issued from
another application, you could turn on query logging and send in an
excerpt from the postmaster log.)

My guess from the rest of his message is something like:

sszabo=# insert into a (a.x) values ('3');
ERROR: syntax error at or near "." at character 17

(from my 7.5 machine).

However, AFAICS in sql92 the above isn't valid, because a.x doesn't meet
the syntactic requirements for elements in the column name list.
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org