Hi!
> > > There's a newer linux-oracle-instantclient-sdk available in the
> > > ports (10.2.0.3), and maybe it helps to compile and link a newer
> > > DBD::Oracle.
> >
> > I have that one (actually, those three), but they are nine
> > years old as well: 20061115_5 is coded into the ports name.
>
Hi!
> > There's a newer linux-oracle-instantclient-sdk available in the
> > ports (10.2.0.3), and maybe it helps to compile and link a newer
> > DBD::Oracle.
>
> I have that one (actually, those three), but they are nine
> years old as well: 20061115_5 is coded into the ports name.
The API did n
According to Kurt Jaeger on Thu, 06/04/15 at 09:38:
>
> My guess: no-one had the need, time and skills to fix it.
>
> There's a newer linux-oracle-instantclient-sdk available in the
> ports (10.2.0.3), and maybe it helps to compile and link a newer
> DBD::Oracle.
I have that one (actually, thos
Hi!
> According to Kurt Jaeger on Thu, 06/04/15 at 02:50:
> > DBD::Oracle no longer supports Oracle client versions before 9.2
> > Try a version before 1.25 for 9 and 1.18 for 8! at ./Makefile.PL line 271.
> >
> > and there is no oracle9-client port on FreeBSD.
>
> Thanks. That makes sense.
According to Kurt Jaeger on Thu, 06/04/15 at 02:50:
>
> DBD::Oracle no longer supports Oracle client versions before 9.2
> Try a version before 1.25 for 9 and 1.18 for 8! at ./Makefile.PL line 271.
>
> and there is no oracle9-client port on FreeBSD.
Thanks. That makes sense. What doesn't ma
Hi!
> What is confusing to me is why FreeBSD _still_ contains
> DBD::Oracle 1.19 in their "ports" tree! After all these years!
Because:
DBD::Oracle no longer supports Oracle client versions before 9.2
Try a version before 1.25 for 9 and 1.18 for 8! at ./Makefile.PL line 271.
and there is no
in message <20150603172207.gf2...@itcom245.staff.itd.umich.edu>,
wrote William Bulley thusly...
>
...
> My focus now is trying to install DBD::Oracle 1.74 from CPAN (from
> April of 2014) on my system.
...
> What is confusing to me is why FreeBSD _still_ contains
> DBD::Oracle 1.19 in their "ports"
According to "Howard, Chris" on Wed, 06/03/15 at 13:09:
>
> I was hoping you could share the actual code
> with us. But no problem. Sounds like you have
> some good clues.
>
> Using Oracle 8 client and ancient DBI libraries
> probably isn't helping, but also seems unlikely to hurt.
>
> I'm le
cat scriptname | od -bc | more
-Original Message-
From: Bruce Johnson [mailto:john...@pharmacy.arizona.edu]
Sent: Wednesday, June 03, 2015 11:13 AM
To: William Bulley
Cc: dbi-users@perl.org
Subject: Re: help with odd DBI perpare/execute errors
> On Jun 3, 2015, at 9:44 AM, Will
> On Jun 3, 2015, at 9:44 AM, William Bulley wrote:
>
> Martin thinks the parsing in the dbd_preparse() function within the
> dbdimp.c file (part of DBD::Oracle) has issues so that it cannot deal
> with the second question mark given the preceding single quote(s).
>
> It seems plausible, yet od
To: Howard, Chris
Cc: Martin J. Evans; dbi-users@perl.org
Subject: Re: help with odd DBI perpare/execute errors
According to "Howard, Chris" on Wed, 06/03/15 at 12:30:
>
> Thanks!
> And what does $query contain?
That is the issue! Martin has worked with me off-line and clearly
th
According to "Howard, Chris" on Wed, 06/03/15 at 12:30:
>
> Thanks!
> And what does $query contain?
That is the issue! Martin has worked with me off-line and clearly
the query contained some quote characters. I've attempted to either
remove those or quote them the DBI quote() way, but since so
Thanks!
And what does $query contain?
-Original Message-
From: William Bulley [mailto:w...@umich.edu]
Sent: Wednesday, June 03, 2015 9:14 AM
To: Howard, Chris
Cc: Martin J. Evans; dbi-users@perl.org
Subject: Re: help with odd DBI perpare/execute errors
According to "Howard,
On 03/06/15 14:06, William Bulley wrote:
Environment Perl script trying to query Oracle 11g database:
FreeBSD 9.3-STABLE
DBI 1.633
oracle8-client 0.2.0
DBD::Oracle 1.19
It seems I missed this ^
A 9 year old DBD::Oracle. I can well believe the preparse code has changed o
!/usr/bin/perl
use strict;
use DBI;
my $dbh= DBI->connect(“dbi:Oracle:host=$host", $user, $pass, {RaiseError =>1});
my $qry1 ='select ? from dual';
my $qry2 = "select ? from dual";
my $sth = $dbh->prepare($qry1);
$sth->execute('foo');
my ($res)=$st
t for x86_64-linux-thread-multi) with:
#!/usr/bin/perl
use strict;
use DBI;
my $dbh= DBI->connect(“dbi:Oracle:host=$host", $user, $pass, {RaiseError =>1});
my $qry1 ='select ? from dual';
my $qry2 = "select ? from dual";
my $sth = $dbh->prepare($qry1);
$sth-&g
According to "Howard, Chris" on Wed, 06/03/15 at 10:44:
>
> Can you post a copy of your prepare statement?
Sure. Here it is:
$sth = $dbh->prepare ($query) or die "Couldn't prepare statement: " .
$dbh->errstr;
Regards,
web...
--
/"\ ASCII RIBBON / William Bulley
\ / CAMP
Can you post a copy of your prepare statement?
-Original Message-
From: William Bulley [mailto:w...@umich.edu]
Sent: Wednesday, June 03, 2015 7:57 AM
To: Martin J. Evans
Cc: dbi-users@perl.org
Subject: Re: help with odd DBI perpare/execute errors
According to "Martin J. Evans&quo
According to Bruce Johnson on Wed, 06/03/15 at
10:10:
>
>
> Make sure your original $query is delimited by double quotes, not single.
I've tried _everything_!!
Single quotes. Double quotes. q{} and qq{} (using the latter now).
But no matter what I try DBI complains about the darn questio
> On Jun 3, 2015, at 6:57 AM, William Bulley wrote:
>
> Yep, I've been all over the net looking for this issue. I am not
> doing anything wrong -- the "invalid string" is the darn "?"!!!
Make sure your original $query is delimited by double quotes, not single.
if you do $sth->prepare(‘selec
According to "Martin J. Evans" on Wed, 06/03/15 at 09:48:
>
> Sounds ok but the error is "invalid string"
>
> ORA-0911
> You tried to execute a SQL statement that included a special character.
>
> http://www.techonthenet.com/oracle/errors/ora00911.ph
On 03/06/15 14:38, William Bulley wrote:
According to "Martin J. Evans" on Wed, 06/03/15 at 09:15:
So, when this fails, what is the value of $value.
I just ran it again. The value is 547.
Sounds ok but the error is "invalid string"
ORA-0911
You tried to execute
According to "Martin J. Evans" on Wed, 06/03/15 at 09:15:
>
> So, when this fails, what is the value of $value.
I just ran it again. The value is 547.
> Assuming you have RaiseError set, you can just put an eval
> around the execute and if $@ is set, print out $valu
workaround described below.
I have a query/prepare setup outside a foreach loop where I execute()
the prepared query something like this, only more complex:
my $query = "select column from table where column = ?";
my $sth = $dbh->prepare ($query);
foreach ()
{
/prepare setup outside a foreach loop where I execute()
the prepared query something like this, only more complex:
my $query = "select column from table where column = ?";
my $sth = $dbh->prepare ($query);
foreach ()
{
$sth->execute($value);
}
I was getting in
On 06/11/13 14:36, Jan Holčapek wrote:
Hi Martin,
On Wed, Nov 6, 2013 at 3:05 PM, Martin J. Evans wrote:
I believe this is a bug in your ODBC driver.
I kind of expected that. I'll file a bugreport to Vertica Support.
good, that was part of what I was hoping to achieve when I did this.
Ho
Hi Martin,
On Wed, Nov 6, 2013 at 3:05 PM, Martin J. Evans wrote:
> I believe this is a bug in your ODBC driver.
I kind of expected that. I'll file a bugreport to Vertica Support.
> However, I took the decision in DBD::ODBC to report this an error and some
> might argue differently. In this cas
t the error/) {
# assume the drop was ok and the table did not exist
# but that is not really a safe assumption to make
} elsif ($@) {
# it is a real error
}
What should have happened is that the driver returned SQL_SUCCESS_WITH_INFO and an
informational msg was retrieved. execute/do
lt;- STORE= 1 at /usr/local/lib64/perl5/DBD/ODBC.pm line 433 via at
./odbctest.pl line 16
SQLExecDirect drop table if exists foo
SQLExecDirect = 1
This means the ODBC API SQLExecDirect was called and it returned 1
(SQL_SUCCESS_WITH_INFO). According to the ODBC spec, when a
1d0)~INNER
'Statement' 'drop table if exists foo') thr#249b010
!!DBD::ODBC unsupported attribute passed (Statement)
STORE DBI::db=HASH(0x270e1d0) 'Statement' => 'drop table if exists foo'
1 <- STORE= 1 at /usr/local/lib64/perl5/DBD/ODBC.pm line 43
oonection string is not correct.
>
> Cheers
>
>
>
> > From: amaresh.poth...@gmail.com
> > Date: Mon, 19 Nov 2012 16:59:09 +0530
>
> > Subject: Perl DBI Hangs while execute()
> > To: dbi-users@perl.org
>
> >
> > Hi All,
> >
> > I am usi
execute()
Hi All,
I am using Perl DBI to connect Oracle Database.
The query runs if type from 'sqlplus' manually but hangs when I use the
sql inside the script.
Getting following error,
"DBD::Oracle::st execute failed: ORA-36871: (XSFTDSC01) Object %s cannot be
used to defin
Well I would do something like
select 1 from dual
rather thatn '*'
It sounds like your DB coonection string is not correct.
Cheers
> From: amaresh.poth...@gmail.com
> Date: Mon, 19 Nov 2012 16:59:09 +0530
> Subject: Perl DBI Hangs while execute()
> To: dbi-
Hi All,
I am using Perl DBI to connect Oracle Database.
The query runs if type from 'sqlplus' manually but hangs when I use the
sql inside the script.
Getting following error,
"DBD::Oracle::st execute failed: ORA-36871: (XSFTDSC01) Object %s cannot be
used to define a colum
Hi, Paul,
I had a similar problem but determined it is not (or at least, mine was
not) a DBI or DBD::mysql issue.
I did find the cause, in my case. I'm not sure how this could happen
and why it would only affect one item out of thousands, but there was
"corruption" in the database itself (I
Did you find a solution to this problem? Cos I'm having the same difficulties.
I have a SQL routine stored in a file, that I wish to run in between
other SQL statements within a perl/DBI script. I wonder, besides to
read that file into a "prepare" statement, is there a way to directly
execute that file from within the perl script? On a second thought,
the
sys
so what does it mean?
http://pastebin.com/iTPCMusG
1.
<- dbd_st_execute 1 rows
2.
-> dbd_st_fetch for 2acbf5c22de0, chopblanks 0
3.
fetch() without execute() error 19 recorded: fetch() without execute()
it means it executed OK? $sth->rows will return 1 bu
have some
encoding issue with our Catalyst application.
then we upgraded the Perl to 5.10.1 and re-build the mod_perl 2.0.4
but in the new server, we keeping getting
DBD::mysql::st fetchrow_array failed: fetch() without execute()
or
DBD::mysql::db selectrow_array failed: fetch() without
1 and re-build the mod_perl 2.0.4
but in the new server, we keeping getting
DBD::mysql::st fetchrow_array failed: fetch() without execute()
or
DBD::mysql::db selectrow_array failed: fetch() without execute()
we have several MySQL servers and all the errors happens with
5.1.39-community-log
_info) which
states the statement has been terminated.
However, it does not get around the fact that SQLExecute is
returning SQL_SUCCESS_WITH_INFO with the broken driver. DBD::ODBC
uses the SQLExecute return to determine if the execute was
successful or not (as per the ODBC docs) and not the state o
tatement has been terminated.
>
> However, it does not get around the fact that SQLExecute is
> returning SQL_SUCCESS_WITH_INFO with the broken driver. DBD::ODBC
> uses the SQLExecute return to determine if the execute was
> successful or not (as per the ODBC docs) and not the s
s_info) which states the statement has
> been terminated.
>
> However, it does not get around the fact that SQLExecute is returning
> SQL_SUCCESS_WITH_INFO with the broken driver. DBD::ODBC uses the SQLExecute
> return to determine if the execute was successful or not (as per the ODBC
&g
ow nulls (the tds_error
packet) then a 01000 informational (tds_info) which states the statement has
been terminated.
However, it does not get around the fact that SQLExecute is returning
SQL_SUCCESS_WITH_INFO with the broken driver. DBD::ODBC uses the SQLExecute
return to determine i
On 18/10/10 23:05, Tim Bunce wrote:
> On Sat, Oct 16, 2010 at 11:03:08AM +0100, Martin J. Evans wrote:
>> On 15/10/2010 22:20, Roode, Eric wrote:
>>> Hello all,
>>>
>>> DBI docs says that statement handle method execute() returns undef on
>>> error.
Roode, Eric schrieb am 18.10.2010 um 13:11 (-0400):
> What is this TDS and where can I learn more about it?
http://en.wikipedia.org/wiki/Tabular_Data_Stream
--
Michael Ludwig
On Sat, Oct 16, 2010 at 11:03:08AM +0100, Martin J. Evans wrote:
> On 15/10/2010 22:20, Roode, Eric wrote:
> >Hello all,
> >
> >DBI docs says that statement handle method execute() returns undef on
> >error. I have found a situation where that does not hold. Was hopi
On Mon, Oct 18, 2010 at 04:45:51PM +0100, Martin J. Evans wrote:
>
> State 23000 you are getting is "Integrity constraint violation" which is an
> error but note the text on the end of the error you are getting:
>
> "[state was 23000 now 01000]"
>
> 01000 is a general warning. I don't understan
On 18/10/2010 18:11, Roode, Eric wrote:
On Monday, October 18, 2010 12:27 PM, Martin J. Evans wrote:
[...]
I looked at this some more and I'm even more sure it is a bug.
The TDS protocol for your situation returns:
tds_error - failed to insert null
tds_info - statement has been terminated
a
On Monday, October 18, 2010 12:27 PM, Martin J. Evans wrote:
[...]
> I looked at this some more and I'm even more sure it is a bug.
>
> The TDS protocol for your situation returns:
>
> tds_error - failed to insert null
> tds_info - statement has been terminated
> a load of done_procs
> the retur
I'm just frustrated at what
>> appears to be a bug in the driver (or possibly DBD::ODBC), and am
>> looking for any way to work around it.
>>
>> My apologies,
>> -- Eric
>>
>>
>
> I was using the Easysoft SQL Server Driver but I also tried with the MS SQ
king for any way to work around it.
>
> My apologies,
> -- Eric
>
>
I was using the Easysoft SQL Server Driver but I also tried with the MS SQL
Server Drivers:
sqlsrv32.dll 14/04/2008 2000.85.1132.00
sqlncli.dll 14/10/2005 2005.90.1399.00
and the first echoed your result and the
S.85%29.aspx
has some interesting info about the STATE that gets returned. In
particular,
it shows that the state code 23000 (which is what I got) means
"Integrity
constraint violation". So I suppose if $sth->execute() returns -1, I
should
also look at $sth->state().
That page a
On Saturday, October 16, 2010 10:08 AM, Martin J. Evans wrote:
> When I run your code with a different driver to MS SQL Server it works
> as I'd expect:
[...]
> print "Execute() returned $exec_retval.\n";
> print 'errstr is"', $sth->errstr, '
On Monday, October 18, 2010 9:24 AM, Martin J. Evans wrote:
> I never meant to offend you with that statement and I agreed it was an
> error.
>
> You are posting on a public list and presumably wanting feedback/help.
> I only know what you've told me, nothing else. Perhaps you might think
> about
On 18/10/10 14:02, Roode, Eric wrote:
> On Saturday, October 16, 2010 6:18 AM, Martin J. Evans wrote:
>
>> On 15/10/2010 22:20, Roode, Eric wrote:
>>> Hello all,
>>>
>>> DBI docs says that statement handle method execute() returns undef on
>>> erro
On Saturday, October 16, 2010 6:18 AM, Martin J. Evans wrote:
> On 15/10/2010 22:20, Roode, Eric wrote:
>> Hello all,
>>
>> DBI docs says that statement handle method execute() returns undef on
>> error. I have found a situation where that does not hold. Was
hopi
On Saturday, October 16, 2010 6:03 AM, Martin J. Evans wrote:
[...]
> As far as I can see this looks like a bug in your driver (but I'll try
> and reproduce here). Surely failing to insert into a column should be
an
> error not success with info (an example of the latter is say an insert
> whic
On 16/10/2010 11:03, Martin J. Evans wrote:
On 15/10/2010 22:20, Roode, Eric wrote:
Hello all,
DBI docs says that statement handle method execute() returns undef on
error. I have found a situation where that does not hold. Was hoping
someone could help me out, maybe there's a worka
race level 15 (instead of 4) would have been slightly more
informative.
Martin
Date: Sat, 16 Oct 2010 11:03:08 +0100
From: martin.ev...@easysoft.com
To: ero...@barrack.com
CC: dbi-users@perl.org
Subject: Re: There's an error, but $sth->execute returns -1
On 15/10/2010 22:20, Roode, Eric
pie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
> Date: Sat, 16 Oct 2010 11:03:08 +0100
> From: martin.
On 15/10/2010 22:20, Roode, Eric wrote:
Hello all,
DBI docs says that statement handle method execute() returns undef on
error. I have found a situation where that does not hold. Was hoping
someone could help me out, maybe there's a workaround.
You need to read further down that
On 15/10/2010 22:20, Roode, Eric wrote:
Hello all,
DBI docs says that statement handle method execute() returns undef on
error. I have found a situation where that does not hold. Was hoping
someone could help me out, maybe there's a workaround.
First, I'm running ActiveState P
Hello all,
DBI docs says that statement handle method execute() returns undef on
error. I have found a situation where that does not hold. Was hoping
someone could help me out, maybe there's a workaround.
First, I'm running ActiveState Perl 5.10.0 on Windows 7, connecting to a
l the data for the first domain in
>> > # the postgres database, @domain2 for the second domain etc..
>> >
>> > print ("GETTING DATA FROM DATABASE\n");
>> > $querystring=("select output_filepath, hostname, logfile from
>> >
e data for the first domain in
> > # the postgres database, @domain2 for the second domain etc..
> >
> > print ("GETTING DATA FROM DATABASE\n");
> > $querystring=("select output_filepath, hostname, logfile from
> > loginf
res database, @domain2 for the second domain etc..
>
> print ("GETTING DATA FROM DATABASE\n");
> $querystring=("select output_filepath, hostname, logfile from
> loginfo");
> $result = $conn->prepare($querystri
fo");
$result = $conn->prepare($querystring);
if ( !defined $result ) {
die "Cannot prepare statement: $DBI::errstr\n";
}
$result->execute;
$i=0;
while ( @row = $result->fetchrow()) {
$this_dom
sql = DBI->connect... (dest)
$sth_as400 = $dbh_as400->prepare...
$sth_as400->execute...
do {
my @row;
my @array_data;
my $sth_pgsql = $dbh_pgsql->prepare...
# fetch each row in array
while (@row = $sth_as400-
@x_values );
>
>
> In your case below you want to bind a single parameter to an array.
> You might have to use |bind_param_array| <#___top> for that
>
> cheers
>
> Denis BUCHER wrote:
>> Tim Bunce a écrit :
>>
>>>> Does someone knows if it&#
The question seems confused...
Yes was difficult to explain ;-)
$sth->execute(%array_data)
%array_data isn't an array, it's a hash.
See http://perldoc.perl.org/perldata.html
Yes absolutely, "associative array" i.e. "hash".
I didn't
>
> Denis BUCHER wrote:
>> Hello,
>>
>> Does someone knows if it's possible to specify an array when executing a
>> prepared statement ?
>>
>> $sth->execute(%array_data)
>>
>> instead of :
>>
>> $sth->execute($array_data["firstname"],array_data["lastname"])
>>
>> Thanks a lot for any help !
>>
>> Denis
>>
>
>
Tim Bunce a écrit :
>> Does someone knows if it's possible to specify an array when executing a
>> prepared statement ?
>
> The question seems confused...
Yes was difficult to explain ;-)
>> $sth->execute(%array_data)
>
> %array_data isn't an array,
I'm using postgresql (Pg)
Denis
John Scoles a écrit :
> Depends on the DBD driver.
>
> Which one are you using?
>
> cheers
>
>
>
> Denis BUCHER wrote:
>> Hello,
>>
>> Does someone knows if it's possible to specify an array when
On Wed, Aug 05, 2009 at 08:19:42PM +0200, Denis BUCHER wrote:
> Hello,
>
> Does someone knows if it's possible to specify an array when executing a
> prepared statement ?
The question seems confused...
> $sth->execute(%array_data)
%array_data isn't an
Depends on the DBD driver.
Which one are you using?
cheers
Denis BUCHER wrote:
Hello,
Does someone knows if it's possible to specify an array when executing a
prepared statement ?
$sth->execute(%array_data)
instead of :
$sth->execute($array_data["firstname"]
Hello,
Does someone knows if it's possible to specify an array when executing a
prepared statement ?
$sth->execute(%array_data)
instead of :
$sth->execute($array_data["firstname"],array_data["lastname"])
Thanks a lot for any help !
Denis
e_identifier('foo','bar', $attr) };
is $called{quote_identifier}, 1;
ok $@, 'quote_identifier callback caused fatal error';
is ref $attr, 'HASH', 'param modified by callback - not recommended!';
I'm calling prepare and execute in
erested in. Callbacks are (still)
> > undocumented, but the test file is pretty clear:
> > http://cpansearch.perl.org/src/TIMB/DBI-1.608/t/70callbacks.t
>
> I was looking at the callbacks a few days ago. I wasn't clear what
> all was available, but more importantly I couldn't see if
ch.perl.org/src/TIMB/DBI-1.608/t/70callbacks.t
I was looking at the callbacks a few days ago. I wasn't clear what
all was available, but more importantly I couldn't see if it was
possible to also get the execute parameters. I assume it's not
possible with the callbacks. Is that c
On Thu, May 07, 2009 at 10:08:52AM -0700, Bill Moseley wrote:
> I can set $DBI::neat_maxlen to have DBI trace output show the complete
> statements, but execute still is truncated.
>
> execute(1, 2, ...)= '0E0' at dbi_neat.pl line 91
>
> Is there an equivalent &q
I can set $DBI::neat_maxlen to have DBI trace output show the complete
statements, but execute still is truncated.
execute(1, 2, ...)= '0E0' at dbi_neat.pl line 91
Is there an equivalent "neat" setting to show all the bind variables?
Also, I want to hook into the
Hi Richard
On Tue, 2008-09-09 at 19:37 -0400, Richard Dice wrote:
> Ron,
>
> This has been the talk of the Perl world for the past few weeks.
> Here's a place you can go as a starting point.
>
> http://perlbuzz.com/2008/08/red-hats-patch-slows-down-overloading-in-perl.html
>
Ahh. $many x $than
Ron,
This has been the talk of the Perl world for the past few weeks. Here's a
place you can go as a starting point.
http://perlbuzz.com/2008/08/red-hats-patch-slows-down-overloading-in-perl.html
Cheers,
- Richard
On Tue, Sep 9, 2008 at 7:03 PM, Ron Savage <[EMAIL PROTECTED]> wrote:
> Hi Ian
Hi Ian
> P.S. Thanks to Clive for his Red Hat/Perl post. In the middle of all this I
> switched hosting services to one that uses CentOS, and I can't believe how
> slow it is.
Hmmm. I realize this is not a CentOS-oriented list, but can you tell us
more about this speed issue? I ask because my
For the record in the hope that somebody may find this helpful.
I finally figured out the problem was simply the wait_timeout value was too
small ( 10 seconds).
The Problem:
Perl would die after a “prepare” call and before execute would return
a DBI trace ended with “my_login skip connect
problem we gave up and moved it to
another server (that had not been upgraded). Worked fine.
They have now upgraded the that system, same problem.
I have tried removing huge chunks of code, split processes in two and still get
the problem.
Execution termination floats around from one execute to
On Tue, June 24, 2008 10:17 pm, Tim_Bunce via RT - [EMAIL PROTECTED] wrote:
> You should avoid using an array to pass arguments to execute().
Why is that? I use it extensively, is it a problem waiting to happen?
John
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 28, 2008 8:04 AM
> To: dbi-users@perl.org
> Subject: How to execute a perl script at remote server
>
> Hi All,
>
>
>
You would be better served to
Hi All,
I have written a Perl script, which deals with the ftp ing
(transferring) the file to remote server and executing a Perl script
(AUT) at remote m/c.
The script is as below and here I have 2 doubts, so please help me to
resolve this.
1) I am getting the message like "
On Wed Apr 02, 2008 at 04:53:36PM +0100, Tim Bunce wrote:
> On Wed, Apr 02, 2008 at 11:55:53AM +0200, Mark Lawrence wrote:
> > After hours of googling and testing I'm down to you guys as my last
> > resort. I have an issue that results in execute() failing with the
> >
On Wed, Apr 02, 2008 at 11:55:53AM +0200, Mark Lawrence wrote:
> After hours of googling and testing I'm down to you guys as my last
> resort. I have an issue that results in execute() failing with the
> error:
>
> not an error(21) at dbdimp.c line 376
> The test scri
On Wed Apr 02, 2008 at 11:55:53AM +0200, Mark Lawrence wrote:
> $dbh->begin_work;
> $sth = $dbh->prepare_cached('INSERT INTO artists(id,name) VALUES(?,?)');
> $res = $sth->execute(1,'one');
> ok(!$res, 'insert duplicate id 1');
> $dbh->co
After hours of googling and testing I'm down to you guys as my last
resort. I have an issue that results in execute() failing with the
error:
not an error(21) at dbdimp.c line 376
The test script below brings out the problem, everywhere except my
development environment. I get the same pr
[EMAIL PROTECTED] wrote:
When I try to run a perl script that uses ODBC drivers to insert data
more than 7 rows I am getting the following error
DBD::ODBC::st execute failed: [unixODBC][FreeTDS][SQL
Server]Procedure has no parameters and arguments were supplied.
(SQL-42000)(DBD
When I try to run a perl script that uses ODBC drivers to insert data
more than 7 rows I am getting the following error
DBD::ODBC::st execute failed: [unixODBC][FreeTDS][SQL
Server]Procedure has no parameters and arguments were supplied.
(SQL-42000)(DBD: st_execute/SQLExecute err=-1
Andy Baumhauer wrote:
Martin,
Thank you so much for the spot on reply. The work you saved with that
reply is greatly appreciated.
Glad to hear it. resmg:wait quantum caught me some time ago when a
complicated query was taking over 8s every now and again and yet running
it outside of the ap
Martin,
Thank you so much for the spot on reply. The work you saved with that
reply is greatly appreciated.
I checked the resource groups with this statement:
COL initial_rsrc_consumer_group FORMAT A24 HEADING 'Resource|Consumer|Group'
COL username FORMAT A12 HEADING '
Andy Baumhauer wrote:
Running DBI 1.58 and DBD::Oracle 1.19 with Oracle 10g (10.2) on Fedora
7 64 bit OS:
Copying a table from one tablespace to another tablespace (two $dbh
handles). The table has 56 fields. I've simplified the process to:
fetch row from first dbh
execute row to s
Running DBI 1.58 and DBD::Oracle 1.19 with Oracle 10g (10.2) on Fedora 7
64 bit OS:
Copying a table from one tablespace to another tablespace (two $dbh
handles). The table has 56 fields. I've simplified the process to:
fetch row from first dbh
execute row to second dbh
commit ever
1 - 100 of 469 matches
Mail list logo
