From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Returning oid or primary key |
Date: | 2001-05-03 17:42:23 |
Message-ID: | 200105031742.f43HgNK08146@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> However, _if_ RETURNING is going to be in the standard SQL for the
> next release, _and_ there are plans to update the jdbc driver to take
> advantage of that in the callable statement, as well, then it makes
> more sense _not_ to add my patch that implements the 'overloading' of
> the return value in the jdbc driver.
>
> I guess the issue is the ability to return the primary key from an
> inserted row, for cases that it's auto-generated, such as using the
> serial type.
Certainly the portable solution is to get RETURNING into the backend so
you can decide what you want to return.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Subhramanya Shiva | 2001-05-03 17:42:44 | How to encode and decode a string as a password field in pgsql table? |
Previous Message | Ned Wolpert | 2001-05-03 17:40:44 | Re: Returning oid or primary key |