Hi,
Can you please clarify my doubts regarding DBI perl module used for
database connection.
In my environment I am using single module to prepare and execute the sql
queries. The sql query can have bind variables or they may not have. In order
to improve performance i used prepare() and
Hard to say without some of the orginal code could be a number of things.
Do you have raiserror or pringerror set on the handle. If you are only
printing an error you may not see it and you end up just rereading the
cached data from the last query.
Post you code so we can have a look at
well this is your problem
my $rc = $sth-execute(@bind) or die Can't execute statement: $DBI::errstr;
You are expecting statement handle $sth to return a recordset into $rc when
it calls the execute method. It does not work like that.
try this
my $sth = $dbh-prepare( q{select ename from emp
On 5/9/07, ramesh thangamani [EMAIL PROTECTED] wrote:
Can you please clarify my doubts regarding DBI perl module used for
database connection.
In my environment I am using single module to prepare and execute the sql
queries. The sql query can have bind variables or they may not have. In
Any thoughts?
Amen: Most of the perl I use only does reads and
the readonly locking could be a big savings.
--
Steven Lembark 85-09 90th Street
Workhorse Computing Woodhaven, NY 11421
[EMAIL PROTECTED]
On Wed, May 09, 2007 at 02:33:23PM -0400, Steven Lembark wrote:
Any thoughts?
Amen: Most of the perl I use only does reads and
the readonly locking could be a big savings.
I trust you'll be sending patches to the authors of the drivers you're
using... :)
Tim.
Hi,
I am not able to install the DBD::Sybase module on solaris 5.8. Even
ppd packages
are not getting installed(I am difficulty in finding one)Can please
somebody help
The error is:
bash-2.03# perl Makefile.PL
Can't find the Client Library include files under
I'm pretty sure that #tmp is a local temporary table, and ##tmp is a
global temporary table...
So the original problem is most likely that the create table #tmp and the
insert into #tmp statements aren't being run on the same physical
connection. I don't know DBD::ODBC, but I can tell you that
