[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: JDBC-JNDI bridge character output.
- To: Erlend Hamnaberg <hamnis@start.no>
- Subject: Re: JDBC-JNDI bridge character output.
- From: Marc Boorshtein <mboorshtein@gmail.com>
- Date: Mon, 18 Jul 2005 16:03:39 -0400
- Cc: openldap-software@OpenLDAP.org
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Cwp8qwu5HqVSHRrApwr8xskhzaI4i8nOv66xFumUQlToSYMIRpxm3jVIWRhb5EDH3oo9uAFxxC5Yz96yHsPPTsVTShwYCEahdkDCXSlVCe9FhPatbMDwMdmEZV3Y5reMAKH4q09ofEZQ0cMy5YLTLGkHVPu6YmRcBTQTiL3tPT4=
- In-reply-to: <42DBE109.4080606@start.no>
- References: <42DBE109.4080606@start.no>
Whats happening is that it's finding that the Norweigan character is
not LDIF safe (though it should be) and so it's base64 encoding it.
1. Which platform is your client?
2. Which platform is your server?
3. Which version of the bridge are you using?
4. If you are using 2.0 (The latest from Octet String's download
site) I would like to know if you can try re-producing this problem
with JLDAP (the library that decided wether or not the data should be
base64 encoded.
On 7/18/05, Erlend Hamnaberg <hamnis@start.no> wrote:
> What character set does the JDBC driver output its data in?
>
> Whenever a word contains the norwegian characters æ ø or å the text gets
> all scrambled up.
>
> FI:
> expected result:
> Bjørn
>
> result from jdbc:
> QmrDuHJu
>
>
> Is it possible to set the output characterset in the connectionsstring
> or do I need to convert the text after it is retrived from the database?
>