Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)

From: Thomas Hallgren <thomas(at)tada(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Mischa Sandberg <mischa(at)ca(dot)sophos(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)
Date: 2006-05-23 07:23:53
Message-ID: 4472B889.5090308@tada.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

Tom Lane wrote:

> I think the hard part of this task is designing the API for access to
> the rowsets from triggers.
>
My preference would be something similar to two Portal instances (the NEW and OLD). I could
then map it in the same way that I map the result of a query. If the API actually used two
real Portal instances, the PL/Java implementation would take minutes.

Regards,
Thomas Hallgren

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Mischa Sandberg 2006-05-23 23:39:56 Re: Porting MSSQL to PGSQL -- triggers
Previous Message Tom Lane 2006-05-22 23:47:46 Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas DCP SD 2006-05-23 07:49:16 Re: error-free disabling of individual child partition
Previous Message Thomas Hallgren 2006-05-23 07:03:36 API changes in patch release