| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Barry Lind <barry(at)xythos(dot)com> |
| Cc: | Dave(at)micro-automation(dot)net, "'PostgreSQL jdbc list'" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Re: [ADMIN] High memory usage [PATCH] |
| Date: | 2001-06-26 19:19:28 |
| Message-ID: | 200106261919.f5QJJSo03998@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-jdbc pgsql-patches |
>
> Having said all of that, I think updateable cursors is a good feature,
> but I think the majority of the work should be done in the backend and
> not in the JDBC driver. The added benefit of this is that then all
> front ends have access to this functionality.
Agreed. This is a backend issue. Updated TODO:
* JDBC
* Comprehensive test suite. This may be available already.
* Updateable resultSet (must be done in backend code)
* Improved DatabaseMetaData
* Compatible blob support
* Error Codes (pending backend implementation)
--
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 | Kristis Makris | 2001-06-26 19:58:51 | Re: Using the extract() function in plpgsql |
| Previous Message | Dave Cramer | 2001-06-26 17:02:01 | RE: RE: [ADMIN] High memory usage [PATCH] |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Harkness | 2001-06-26 20:48:04 | Re: High Memory Usage Patch -- Disregard my last message |
| Previous Message | Dave Cramer | 2001-06-26 17:02:01 | RE: RE: [ADMIN] High memory usage [PATCH] |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Harkness | 2001-06-26 20:48:04 | Re: High Memory Usage Patch -- Disregard my last message |
| Previous Message | Dave Cramer | 2001-06-26 17:02:01 | RE: RE: [ADMIN] High memory usage [PATCH] |