Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-22 Thread Albe Laurenz
Durumdara wrote: [client_encoding is switched to WIN1250] > And what happening what DB recognize not win1250 character in SQL? > Is it converted to "?" or an exception dropped? > And if the UTF db contains non win1250 character? > Is it replaced in result with "?" or some exception dropped? What y

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-21 Thread Durumdara
Hi! 2009/12/21 Albe Laurenz > Durumdara wrote: > >> - Change the client encoding to WIN1250 (e.g. by > >> setting the environment variable PGCLIENTENCODING). > > > > So if I have Python and pygresql, can I set this value in Python? > > The main problem that I don't want to set this value globall

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-21 Thread Albe Laurenz
Durumdara wrote: >> - Change the client encoding to WIN1250 (e.g. by >> setting the environment variable PGCLIENTENCODING). > > So if I have Python and pygresql, can I set this value in Python? > The main problem that I don't want to set this value globally > - possible another applications want

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-21 Thread Alban Hertroys
On 21 Dec 2009, at 10:26, Durumdara wrote: > So if I have Python and pygresql, can I set this value in Python? > The main problem that I don't want to set this value globally - possible > another applications want to use another encoding Sure you can, just execute SET client_encoding TO 'WIN

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-21 Thread Martijn van Oosterhout
On Mon, Dec 21, 2009 at 10:26:51AM +0100, Durumdara wrote: > So if I have Python and pygresql, can I set this value in Python? > The main problem that I don't want to set this value globally - possible > another applications want to use another encoding... Each connection can set the encoding to w

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-21 Thread Durumdara
Hi! 2009/12/19 Albe Laurenz > If you need the data in WIN1250 on the client side, change the client > encoding to WIN1250. > > So: > - Create the database with UTF8. > - Change the client encoding to WIN1250 (e.g. by setting the environment > variable PGCLIENTENCODING). > - Import the dump of th

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-19 Thread Albe Laurenz
Durumdara wrote: > I have a software that uses Postgresql. This program (and website) developed > and working on Window (XP/2003), > with native charset (win1250). > > Prior week we got a special request to install this software to a Linux > server. > > Yesterday I installed Ubu9.10 on VirtualBox

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-19 Thread Adrian Klaver
On Saturday 19 December 2009 1:04:30 pm Dave Page wrote: > On Sat, Dec 19, 2009 at 8:54 PM, Adrian Klaver wrote: > >> The Windows version of PG and Admin is not supports collation, so these > >> two options are disable (collation, character type). > > > > There is a Linux version of PGAdmin availa

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-19 Thread Dave Page
On Sat, Dec 19, 2009 at 8:54 PM, Adrian Klaver wrote: >> The Windows version of PG and Admin is not supports collation, so these two >> options are disable (collation, character type). > > There is a Linux version of PGAdmin available for Ubuntu 9.10. Doesn't matter - pgAdmin supports collation a

Re: [GENERAL] Charset Win1250 on Windows and Ubuntu

2009-12-19 Thread Adrian Klaver
On Friday 18 December 2009 4:30:46 am Durumdara wrote: > Hi! > > I have a software that uses Postgresql. This program (and website) > developed and working on Window (XP/2003), with native charset (win1250). > > Prior week we got a special request to install this software to a Linux > server. > > Y