| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Dave Cramer <Dave(at)micro-automation(dot)net> |
| Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: updatable (J2EE) resultsets |
| Date: | 2002-12-24 17:57:53 |
| Message-ID: | Pine.LNX.4.33.0212241249590.6607-100000@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 23 Dec 2002, Dave Cramer wrote:
> BTW, I only apply to the HEAD, we have never patched to the current
> version. Barry and I have talked about it recently, obviously you think
> this is "abnormal". What are your opinions about it?
>
This means that the driver we ship with 7.3.0 will be exactly the same as
7.3.1 and 7.3.2 and so on. The .0 release of the server and the driver
will generally bring about the discovery of bugs in both. The server bugs
are fixed and a new release is put out .1, but the driver bugs are only
fixed in HEAD and our only advice is to run a driver from CVS head. This
is something our users don't want to do because it requires a cvs checkout
and running untested code. I think the policy for the driver should match
that for the server: new features go into HEAD while bug fixes go into
both the stable and development branches.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Serodio | 2002-12-24 18:23:12 | Re: updatable (J2EE) resultsets |
| Previous Message | Barry Lind | 2002-12-24 17:01:42 | Problem with move not returning number of rows affected [was: error when using move, any suggestions?] |