Hi,
I am in the process of moving some select SQL which was in Perl into
functions and procedures in an oracle package which return a cursor the
perl can read i.e., to hide the SQL from outside the database. Some of
these select statements read clobs.
create table martin (x clob);
In perl
Ouch nasty one Martin.
But I think that DBD oracle is doing the correct thing here.
I think when you bury the 'SELECT x from martin; ' in the SP like this
you are essentially only ever going to get a lob locater back as that is
what you are asking for.
Of couser you could use all the neat
John Scoles wrote:
Ouch nasty one Martin.
But I think that DBD oracle is doing the correct thing here.
Well that is what I'm after clarification on. The pod for ora_auto_lob
says retrieves the contents of the CLOB or BLOB column in most
circumstances. What are the circumstances it does
Martin Evans wrote:
John Scoles wrote:
Ouch nasty one Martin.
But I think that DBD oracle is doing the correct thing here.
Well that is what I'm after clarification on. The pod for ora_auto_lob
says retrieves the contents of the CLOB or BLOB column in most
circumstances. What are the
Further to my problems with lobs in Oracle the following code works fine
in DBD::Oracle 1.20 and seg faults in DBD::Oracle 1.21. The key seems to
be that the returned cursor points to 2 rows. If the do calls which
insert into the table are reduced to 1, there is no problem. Likewise,
if the
On Thu, Jul 17, 2008 at 7:19 PM, gene golub [EMAIL PROTECTED] wrote:
1. how do you process procedures
Often the same or nearly the same way you process other SQL statements.
There are often examples in the DBD::* (whatever DBD you are using)
documentation.
2. what if I have multiple select or
Hi Martin I found the bug (well actually an omission) and fixed it so
now It will return the data you expect.
I committed the changes to Trunk
http://svn.perl.org/modules/dbd-oracle/trunk so if you will try the code
from there and see if it works for you now.
Seem the not all the
