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

RE: [INTERFACES] JDBC and character sets

From: Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk>
To: "'David Warnock'" <david(at)sundayta(dot)co(dot)uk>, Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk>
Cc: "'Herouth Maoz'" <herouth(at)oumail(dot)openu(dot)ac(dot)il>, pgsql-interfaces(at)postgresql(dot)org
Subject: RE: [INTERFACES] JDBC and character sets
Date: 1999-06-23 07:11:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
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.


Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.

-----Original Message-----
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?

David Warnock
Sundayta Ltd


pgsql-interfaces by date

Next:From: Alexander SchneiderDate: 1999-06-23 11:08:45
Subject: What options in pg_Connect?
Previous:From: Peter MountDate: 1999-06-23 07:03:18
Subject: RE: [INTERFACES] Arrays in PostgreSQL

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