It shouldn't bloat the driver by that much. As we already issue a few
queries on startup, I'll add a suggested test, and if that works ok, I
should have UNICODE support done by the end of the weekend.
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.
From: David Warnock [mailto:david(at)sundayta(dot)co(dot)uk]
Sent: Tuesday, June 22, 1999 5:46 PM
To: Peter Mount
Cc: 'Herouth Maoz'; pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] JDBC and character sets
Obviously I agree 100% that supporting unicode should not break existing
applications or code.
How about either a extra parameter to the creation of a connection?
If it is easier to keep this very separate I don't mind a completely
separate jar file/driver at least to start with. After all most people
won't yet be using this feature so why bloat their driver?
pgsql-interfaces by date
|Next:||From: Alexander Schneider||Date: 1999-06-23 11:08:45|
|Subject: What options in pg_Connect?|
|Previous:||From: Peter Mount||Date: 1999-06-23 07:03:18|
|Subject: RE: [INTERFACES] Arrays in PostgreSQL|