RE: JDBC Patch

The problem is that there are so many different places it can go. I was
thinking of moving the version stuff into DriverClass.java (which is built
dynamically by make), but I'm not sure how adding malefile.global would
affect the compilation process.

However, JDBC needs:

Full string: "7.0.2"
Major version: 7
Minor version: 0

and those are just from memory.

If I get chance today, I'll look into it.

Peter

--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount(at)it(dot)maidstone(dot)gov(dot)uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council

-----Original Message-----
From: Peter Eisentraut [mailto:peter_e(at)gmx(dot)net]
Sent: Friday, August 25, 2000 9:28 AM
To: Peter Mount
Cc: 'Christopher Cain'; pgsql-interfaces(at)postgresql(dot)org;
pgsql-patches(at)postgresql(dot)org
Subject: RE: [INTERFACES] JDBC Patch

Peter Mount writes:

> Hmmm, I thought I had caught all the version strings. Thanks for spotting
> it.

Peter, you can avoid this sort of thing in the future. Makefile.global
defines a variable `VERSION' that you should compile into the binaries.
I'm not sure exactly how it would work with Java, but perhaps something
like this:

javac -Dversion='"$(VERSION)"' xyz.java

or run sed before the compilation.

--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden