From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at> |
Cc: | Hannes Dorbath *EXTERN* <light(at)theendofthetunnel(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: DBI-Link, Oracle, database encoding |
Date: | 2006-10-27 18:27:06 |
Message-ID: | 20061027182706.GI24218@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Oct 27, 2006 at 09:05:44AM +0200, Albe Laurenz wrote:
> David Fetter wrote:
> >> I know about Oracle, but have not yet managed to setup DBI-Link.
> >
> > Try it again :)
> > http://pgfoundry.org/projects/dbi-link/
>
> I will try again when the need arises and/or when I find time :^)
Great :)
> >> NLS_LANG need to be set in the environment of the process using
> >> the Oracle client.
> >
> > Is there some way to set this in the connection string for DBI?
>
> You, the author of DBI-Link, know more about DBI than I do.
Not necessarily. This is a Perl and Oracle issue. DBI-Link just uses
DBI's facilities without further elaboration.
> My guess: No.
> You cannot pass the desired codepage to Oracle client at connect
> time.
Good to know.
> The only possible way to tell Oracle client what codepage you want
> is with the environment variable NLS_LANG. Also, you cannot change
> the client codepage during a session. Don't ask me why they designed
> it that way.
I'm sure it seemed like a good idea at the time ;)
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Sandro Dentella | 2006-10-27 18:48:30 | Simple OUTER JOIN doubt |
Previous Message | Matthias Lüdtke | 2006-10-27 18:12:21 | Modifying SQL parser with extensions? |