pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Michael M Friedel <mfl@betty-tv.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Question about update syntaxt
Date: Fri, 29 Apr 2005 20:51:37 -0700 (PDT)
Message-ID: <20050429203821.L60676@megazone.bigpanda.com> (raw)
In-Reply-To: <5BD9C777-3A63-4A00-8B4B-F1BB5C230893@betty-tv.com>
References: <5BD9C777-3A63-4A00-8B4B-F1BB5C230893@betty-tv.com>

On Fri, 29 Apr 2005, Michael M Friedel wrote:

> I am trying to use an application (Through ODBC) that uses the
> following update syntax
>
> UPDATE MyTable SET MyTable.id=2 WHERE id=1
>
> unfortunatly I get an error message
>
> ERROR:  column "mytable" of relation "mytable" does not exist
>
> Question is, is ther something I can configure that will make
> Postgresql accept these kind of statments ?

I don't believe there's a way to make the server itself accept that. IIRC,
past discussions usually have bogged down into questions of whether to
support the syntax since it doesn't appear to be valid SQL and if so what
semantics to give cases where the tablename doesn't match. I'm not sure if
there's any way to get the ODBC driver to do something about it, however.




view thread (2+ messages)

Message-ID: <20050429203821.L60676@megazone.bigpanda.com>
Permalink:  ../20050429203821.L60676@megazone.bigpanda.com/
Also on:    postgresql.org/message-id/20050429203821.L60676@megazone.bigpanda.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: sszabo@megazone.bigpanda.com, mfl@betty-tv.com
  Subject: Re: Question about update syntaxt
  In-Reply-To: <20050429203821.L60676@megazone.bigpanda.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox