On Tue, 7 Mar 2006 00:27:36 +0000, Tim Bunce <[EMAIL PROTECTED]> wrote:
> Blame Oracle.
You know I do. All the time.
/we hates oracle, /we do
> Or blame me - for a decision I made many many years ago now to switch
> from binding strings as type 5 (STRING) to type 1 (VARCHAR2).
> Oraperl used to use 5 but that type doesn't support embedded \0 bytes.
> Type 1 does support embedded nul bytes but has it's own set of issues.
>
> You can choose your own poison via the $dbh->{ora_ph_type} attribute.
>
> See also http://search.cpan.org/src/PYTHIAN/DBD-Oracle-1.17/t/40ph_type.t
I hope for a quick, maybe dirty, workaround from John, as this is what causes
serious injury in a customer database, and I don't know how to fix it.
--
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.9.x on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.0, AIX 4.3 & 5.2, and Cygwin. http://qa.perl.org
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org
http://www.goldmark.org/jeff/stupid-disclaimers/
