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.
Enterprise Support Officer, Maidstone Borough Council
All views expressed within this email are not the views of Maidstone Borough
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;
Subject: RE: [INTERFACES] JDBC Patch
Peter Mount writes:
> Hmmm, I thought I had caught all the version strings. Thanks for spotting
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
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
pgsql-patches by date
|Next:||From: Bryan Field-Elliot||Date: 2000-08-25 18:25:22|
|Subject: JDBC and java.sql.Timestamp|
|Previous:||From: Peter Mount||Date: 2000-08-25 06:29:41|
|Subject: RE: JDBC Patch|
pgsql-interfaces by date
|Next:||From: Cedar Cox||Date: 2000-08-25 08:49:32|
|Subject: Re: JDBC problem|
|Previous:||From: Peter Mount||Date: 2000-08-25 06:33:57|
|Subject: RE: using large objects with jdbc|