| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Roadmap for FE/BE protocol redesign |
| Date: | 2003-03-12 00:34:15 |
| Message-ID: | Pine.LNX.4.44.0303120107410.1617-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
Dave Page writes:
> I don't know about JDBC, but ODBC could use it, and it would save a heck
> of a lot of pain in apps like pgAdmin that need to figure out if a column
> in an arbitrary resultset might be updateable.
Strictly speaking, result sets are never updatable, because there's no way
you can refer to a result set and tell the system to update it. So let's
hear what you *really* need and then consider interfaces for *that*.
Maybe updatable views or updatable cursors?
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sumaira Ali | 2003-03-12 00:42:55 | bitmask for lock types |
| Previous Message | Dave Cramer | 2003-03-11 23:20:09 | Request for quote |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-03-12 00:34:55 | Re: permanently setting PROMPT1 |
| Previous Message | Charles Hauser | 2003-03-11 23:39:51 | permanently setting PROMPT1 |