db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Fischer <fisc...@seitenbau.net>
Subject RE: Postgresql table aliases
Date Thu, 12 Nov 2009 15:20:36 GMT
> I also wonder if this isn't a PostGres version issue.  If I remember the
> SQL standards correctly, the query that PostGres is choking on is
perfectly
> valid SQL.  PostGres, like MySQL and the like, have all been working to
> follow the SQL Standard more closely.  This could be a standards bug in
> your version of PostGres.

I checked that postgres 8.4 indeed chokes on updates with fully qualified
column names. Dunno about earlier versions.

> > ...
> > > ...
> > > Now I'm trying to migrate everything for Postgresql but the main
> > problem
> > > is that when
> > > I execute an UPDATE query I receive an error from torque, because the
> > > update query automatically
> > > generated are of the form
> > >     update a set a.b = c;
> > > that in PostgreSQL it's an error because table name can't be a prefix
> > > for a column in set statement.


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org


Mime
View raw message