Thread: Could not find commit messages for the changelog
Hi,
I was looking into what has exactly changed against a particular changelog in 8.3-600. 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? Here are the three issues that were not found in pgjdbc-commit archives.
Can anybody tell me where to find the patch of the above mentioned items.
--Altaf Malik
Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
I was looking into what has exactly changed against a particular changelog in 8.3-600. 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? Here are the three issues that were not found in pgjdbc-commit archives.
- Add methods to PGInterval to combine and scale intervals. (jurka)
- Make the default object return type of oids to be a Java Long instead of Integer because oids are unsigned and exceed the range of Integer. (jurka)
- Fix the error message generated by a CallableStatement not getting results that match the registered out parameters to report the correct parameter position. (jurka)
Can anybody tell me where to find the patch of the above mentioned items.
--Altaf Malik
Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
On Thu, 26 Apr 2007, Altaf Malik wrote: > I was looking into what has exactly changed against a particular > changelog in 8.3-600. 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? If they're in the changelog then they're in the release. The changelog is not a place to put speculation on possible future improvements. > Add methods to PGInterval to combine and scale intervals. (jurka) http://gborg.postgresql.org/pipermail/pgjdbc-commit/2007-April/000609.html > Make the default object return type of oids to be a Java Long instead > of Integer because oids are unsigned and exceed the range of Integer. > (jurka) http://gborg.postgresql.org/pipermail/pgjdbc-commit/2007-February/000584.html > Fix the error message generated by a CallableStatement not getting > results that match the registered out parameters to report the correct > parameter position. (jurka) > http://gborg.postgresql.org/pipermail/pgjdbc-commit/2007-March/000599.html Kris Jurka