RE: [phplib] Long session strings and Oracle From: Francesco.Marsan <email protected>
Date: 06/26/00

I worked around this problem using CT_Split_Sql, which works fine for me.

I think there could be another solution ... I've seen a posting in the php-oracle list, saying that one should use the ocibindbyname() function to store those long strings in a LONG field. From what I understand ocibindbyname() should be called after ociparse(), before ociexecute(). This means that db_oci8.inc should be subclassed, but I don't know if this can be done in an easy way.

Any ideas?

-f
-----Original Message-----
From: Kevin Porterfield [mailto:kpmd <email protected>]
Sent: Monday, June 26, 2000 12:06 PM
To: phplib <email protected>
Subject: [phplib] Long session strings and Oracle

I saw a thread here earlier about problems with Oracle's LONG datatype and
string session info. The problem is that Oracle's LONG datatype will only
store string literals of up to 2000 characters... not enough. if you go over
that Oracle spits out the error:

ORA-01704: string literal too long

What I haven't seen on this list is a solution. I see many people using
phplib with Oracle, so I am wondering if any of them are using sessions and
how they managed to work around this problem.

Any info would be greatly appreciated...

kp
kpmd <email protected>

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>