| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: lastval() |
| Date: | 2005-05-09 04:10:02 |
| Message-ID: | Pine.LNX.4.44.0505090605450.7072-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Sun, 8 May 2005, Tom Lane wrote:
> Why is that a good idea? In a complex application it'd be awfully easy
> to break logic that depends on such a thing.
Of course it can break. currval() can also break in a complex application
with triggers and rules that do things the developer does not expect.
There are however lots of cases where it is safe and useful. Not the least
when you want to port an application that uses similar features.
--
/Dennis Björklund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2005-05-09 04:21:09 | Re: lastval() |
| Previous Message | Satoshi Nagayasu | 2005-05-09 04:03:10 | Re: Oracle Style packages on postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2005-05-09 04:21:09 | Re: lastval() |
| Previous Message | Tom Lane | 2005-05-09 03:54:06 | Re: [PATCHES] Cleaning up unreferenced table files |