Re: Apparent DBD::Oracle 1.16 unicode regression
From: Lincoln A. Baxter (lab_at_lincolnbaxter.com)
Date: 12/02/04
- Next message: Lincoln A. Baxter: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Previous message: Tim Bunce: "Re: DBIx::DBH - Perl extension for simplifying database connectio ns"
- Maybe in reply to: Lincoln A. Baxter: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Next in thread: Jesse Vincent: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Reply: Jesse Vincent: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Jesse Vincent <jesse@bestpractical.com> Date: Wed, 01 Dec 2004 18:59:18 -0500
On Wed, 2004-12-01 at 12:18 -0500, Jesse Vincent wrote:
> The bug I'm describing isn't something
> I've managed to duplicate in-house. Everyone who's hitting it is
> running perl 5.8.3 or newer (Some are running 5.8.5). They're all
> running against Oracle 9.2.0.x.
So, you are allowing them to make a direct oracle connection? Assuming
you are, then, can you ask one of those complaining to at least provide
you with the output requested?
I suspect an oracle client version mismatch with the server.
If the build make tests run clean (against YOUR database), and their
environment does not match the exceptions skipped, then it is most
likely be an environment issue for their application.
Lincoln
- Next message: Lincoln A. Baxter: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Previous message: Tim Bunce: "Re: DBIx::DBH - Perl extension for simplifying database connectio ns"
- Maybe in reply to: Lincoln A. Baxter: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Next in thread: Jesse Vincent: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Reply: Jesse Vincent: "Re: Apparent DBD::Oracle 1.16 unicode regression"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|