Why NONE encoding is evil ? It is stupide to charge especially servers for encoding and decoding charsets., It can be done at the final end only and there is all in java to do that easely.

--- On Mon, 8/13/12, Roman Rokytskyy <roman@...> wrote:

From: Roman Rokytskyy <roman@...>
Subject: Re: [Firebird-Java] Re: Java CharSet to Firebird CharSet
To: Firebird-Java@yahoogroups.com
Date: Monday, August 13, 2012, 1:02 AM
















 









> I would like to connect using the current charset from O.S, so i cannot hard-code a string, be it in the "charSet" or "encoding" property, as my application can run in different O.S or in the same O.S but with different charset.



In case of Java the connection charset has little to do with the OS, but

rather with the encoding of data in the database. Only if data in the

database are in NONE encoding and are being populated via fbclient.dll

in the OS charset, then what you write makes sense. But only on that

particular computer. And NONE encoding is evil anyway. :)



Roman

























[Non-text portions of this message have been removed]