Re: RETURNING and DO INSTEAD ... Intentional or not?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> FYI, after some tinkering around, I've found that RETURNING is 100%
>> incompatible with any table which has conditional DO INSTEAD rules; there's
>> just no way to make it work and return any intelligible data. This would be
>> a completely corner case, except that people use conditional DO INSTEAD rules
>> heavily with partitioning (and yes, real users are complaining).
>
> Those would be real users who are not on any PG mailing list? Cause I
> have not seen any complaints, much less any proposals for a solution...

The majority of our users do not sit on a postgresql mailing list. They
sit on php-db, hibernate, perl-dbd etc...

Sincerely,

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6rUGATb/zqfZUUQRAib4AJ9I+/PvPCOutHJVZYdOgsDyt2WveACcDbyw
V/jt2lJquaQ3O4azJumfYUs=
=GhO1
-----END PGP SIGNATURE-----