Skip site navigation (1) Skip section navigation (2)

Re: Could not find commit log for changelogs

From: Kris Jurka <books(at)ejurka(dot)com>
To: Altaf Malik <mmalik_altaf(at)yahoo(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Could not find commit log for changelogs
Date: 2007-01-16 17:36:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc

On Tue, 16 Jan 2007, Altaf Malik wrote:

>   I was looking into what has exactly changed against a particular 
> changelog in 8.2-504. I found few issues which are reported in the 
> changelog but are not in pgjdbc-commit archives. Can anybody tell me if 
> these changes are really in the latest code? or if they are planned to 
> be included in next release? But then why are they in changelog? Here 
> are the four issues that were not found in pgjdbc-commit archives.

I sometimes reword the changelog to be a little more understandable than 
the original commit message.  So all of these items are in the release and 
should be available in the archives.

>     Improve handling of incorrectly written user code using 
> CallableStatements. Defend against trying to retrieve data before the 
> statement is executed. (jurka)

OK, this one seems to be missing from the archives, but see revision 1.93 

>     Adjust precision returned by meta data methods to reflect the latest 
> javadocs additional documentation. (jurka)

>     Correct error message in CallableStatement to identify the mismatch 
> with the registered return type. (jurka)

>     Correct escaping of named savepoints which follow identifier, not 
> literal rules. (jurka) Thanks to Michael Paesold.

Kris Jurka

In response to

pgsql-jdbc by date

Next:From: Votilla, Mike # PittsburghDate: 2007-01-16 21:00:46
Subject: Message / Error Handler
Previous:From: Altaf MalikDate: 2007-01-16 14:28:31
Subject: Could not find commit log for changelogs

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group