Re: Compiere ERP and SQL quirks

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Marek Mosiewicz" <marekmosiewicz(at)poczta(dot)onet(dot)pl>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Compiere ERP and SQL quirks
Date: 2005-01-07 17:14:35
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A759C@Herge.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marek Mosiewicz wrote:
> Hello
>
> We made Compiere (Open source ERP system) to Firebird (Fyracle)
> This is special version of Firebird with added Oracle compatibility
> (Oracle
> PL/SQL).
> It made porting much easier, but our experience show that it
> would be now also not very difficult with other databases like
PostgreSQL.
>
> Compiere contained lot of PL/SQL which size is now largely reduced.
> Main problem is some SQL constructions which are not supported.
> Particulary something like this is very important:
> UPDATE sometable set (col1,col2) = (select col_a,col_b from
> another_table
> where ....)
> This construction seems to be quite useful in another cases.
>
> Would be it diffcult and possible to add such syntax to PostgreSQL ?

PostgreSQL has limited support for the SQL 92 row constructor. You can
use it in select expressions in most places, but not in update as you
noticed.

Be forewarned that row constructor expressions involving the > or <
operators can give the wrong answer:

select (2,2,3) > (2,1,3)
returns false when it should return true.

Merlin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew T. O'Connor 2005-01-07 17:26:43 Re: [Testperf-general] pg_autovacuum w/ dbt2
Previous Message Tom Lane 2005-01-07 17:14:08 Re: Porting/platforms/buildfarm open issues