Hi,
The problem is on SET statement... I've tested with postgresql 8.2
and 8.3.
Both worked with alias, but that only for WHERE statement, as follows:
UPDATE "schema1"."table1" AS "P"
SET "id"='1', "field2"=now()
WHERE "P"."id" in ('1')
The problem is postgresql doesn't accept SET "P"."id" sin
and yet this error is still around even with the latest branch? has it
been broken again?
On Feb 15, 12:23 pm, nate <[EMAIL PROTECTED]> wrote:
> Please do everyone else a favor and search around a little bit next
> time. This bug has already been reported a zillion times, and was
> fixed weeks a
Please do everyone else a favor and search around a little bit next
time. This bug has already been reported a zillion times, and was
fixed weeks ago.
On Jan 21, 8:58 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I'm having trouble making UPDATE queries in PostgreSQL. I know that
> there
On Thu, Feb 14, 2008 at 5:11 PM, Blackshack <[EMAIL PROTECTED]> wrote:
>
> I have the same problem so i wrote a correctif not a patch but soon i
> wrote a good patch to correct the update pb for postgresql.
> This correctif solve the problem for simple update and update with
> join conditions.
I have the same problem so i wrote a correctif not a patch but soon i
wrote a good patch to correct the update pb for postgresql.
This correctif solve the problem for simple update and update with
join conditions.
In the file dbo_source.php at the line 1245 : you replace the line:
case 'update':
I'm having trouble making UPDATE queries in PostgreSQL. I know that
there is a known issue about Postgres not supporting aliases in UPDATE
queries. Anyway, my problem is that when I try to create new Aro like
this:
$parent = $this->Acl->Aro->findByAlias('SuperUser');
