insert into alerts (alrt, ncmp, suno, mess, prty, spst, dnst, crea, cdat)
values ('$max_alert', '$company','$supplier', '$message',
'$priority', '2',
'2', '$userid', SYSDATE)
This works fine unless there is a single quote in the message, which
obviously is a big problem
On Tue, Oct 22, 2002 at 12:47:31PM -0400, Jeff Urlwin wrote:
I'd check on your versions of FreeTDS and unixODBC...
So FreeTDS is broken, not DBD::ODBC, despite isql not showing the same
behaviour? If so i'll go and see if i can report a bug in that.
--
dave thorn | [EMAIL PROTECTED]
Try doing the disconnect inside the signal handler.
But be aware that doing _anything_ in perl inside an asynchronous
signal handler is prone to problems.
Also be aware that signal handling has changed in perl 5.8 and
you may well find you have a different set of problems then.
Tim.
On Wed,
On Tue, Oct 22, 2002 at 08:37:34PM -0400, Steve Sapovits wrote:
Looks like an Oracle error, which is what I'd expect. I'm just
wondering if Oracle is supposed to support this or not ...
Here's the trace output (sorry for any wrapping):
- prepare for DBD::Oracle::db
On Wed, 23 Oct 2002 16:54:25 +1000, Mike McCauley wrote:
# Run this for a few secs, then unplug from the network.
# the execute times out,tries
# to disconnect, get internal error
If you pull the plug, the disconnect() cannot possibly work either.
--
Bart.
Hi Bart,
On Wed, 23 Oct 2002 20:53, Bart Lateur wrote:
On Wed, 23 Oct 2002 16:54:25 +1000, Mike McCauley wrote:
# Run this for a few secs, then unplug from the network.
# the execute times out,tries
# to disconnect, get internal error
If you pull the plug, the disconnect() cannot possibly
Hi Tim and all,
On Wed, 23 Oct 2002 20:40, Tim Bunce wrote:
Try doing the disconnect inside the signal handler.
Interesting thought, but alas it didnt work.
Still get the same internal error and core dump when disconnect is called.
I couldnt really see anything relevant in the Oracle API
Andreas Schmitz wrote:
what about this one?
my $max_alert = param(max_alert);
$max_alert =~ s/(['])/$1$1/g;
my $sth = qq[insert into alerts (alrt, ncmp, suno, mess, prty, spst,
dnst, crea, cdat) values (\'$max_alert'\, \'$company'\, \'$supplier'\,
\'$message'\, \'$priority'\, \'2'\,
One I've not release yet. You may need to make the changes by hand.
Tim.
On Wed, Oct 23, 2002 at 06:53:37AM -0400, Steve Sapovits wrote:
Tim - what version of DBD::Oracle are you starting with? Thanks ...
Tim Bunce wrote:
On Tue, Oct 22, 2002 at 08:37:34PM -0400, Steve Sapovits wrote:
Hello All,
I've got the following problem:
Using DBD::PgPP for Postgres works fine, as long as I don't do a fetch
indside of a fetch. Running the following code:
Tim,
Thank you very much.
I would like to know, if Perl5 is existing installed, in
/usr/local/perl5/lib... can I try to install DBI and DBD in some other
dir_path say: /home/sched/opwsched/devtools . If yes, is it with simple
Install command or any other.
Please let me know. Because I tried
On Wed, Oct 23, 2002 at 03:10:05PM +0200, Stephan Harren wrote:
Hello All,
$statement=SELECT device_id FROM devices WHERE monitor=true;
$st1=$db1-prepare($statement) or $err=$DBI::errstr;
$statement=SELECT
ip,probes,packetloss,duration,last_check,sms,mail FROM
Hey Mike,
The OCI-21500 is definitely an Oracle problem. It's like the dreaded
ORA-600 error in that it should never happen. The main difference is that
OCI-21500 is a client problem.
Are you running an unpatched client (9.0.1.0.0)? If so, you'll want the
183MB 9.0.1.4.0 Linux patch from
Looks like a DBD::PgPP bug.
Tim.
Thanks, any advices (another driver, for example DBD:Pg, btw, do I need
libpq.so at runtime or just at build time?) ?
Best regards,
Stephan
--
Stephan Harren
Manager Site Operations
MFN-IS Germany
Tel +49 69 90554 153
Cell +49 173 7011126
Fax +49 69 90554
On Tue, 22 Oct 2002 13:43:49 -0600
Powell, Bruce [EMAIL PROTECTED] wrote:
At a client site we just installed DBD/dbi. Upon starting up our
product that uses this method to connect with the database we received
this error:
This is typical problem with standard PERL+DBD::Oracle installation.
Dave,
I really can't tell, without configuring what you have and you seem to be
unable to describe your versions, etc, nor can you update to the latest
DBD::ODBC...sowhat I will conclude is:
It *may* be a bug in DBD::ODBC.
It *may* be a bug in FreeTDS
It *may* be a bug in unixODBC (sorry
Hello all,
I'm having difficulties getting Oracle 9i and DBD 1.12 to work together on
Solaris 8 (5.8). After following the advice of previous threads on this
group, I have converted all of the references in Makefile.PL from
$OH/lib -- $OH/lib32, which fixes the compile time problems. However,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 23 October 2002 17:53, Stephan Harren wrote:
Thanks, any advices (another driver, for example DBD:Pg, btw, do I
need libpq.so at runtime or just at build time?) ?
Yes, you need it at runtime. Worth using, IMO. It's faster, has all the
On Wed, 23 Oct 2002 08:06:42 -0400 Christopher G Tantalo [EMAIL PROTECTED] wrote:
what about this one?
my $max_alert = param(max_alert);
$max_alert =~ s/(['])/$1$1/g;
my $sth = qq[insert into alerts (alrt, ncmp, suno, mess, prty, spst,
dnst, crea, cdat) values (\'$max_alert'\,
Hi,
I got a brand new RS/6000 machine, I just installed the AIX 5.1,
and the two packages perl 5.6.1 and MySQL, both are
from AIX Toolbox.
Now I need to install the DBI so I can use Perl to access the MySQL
database. I download DBI-1.30 from
Hi, Todd,
Thanks to your reply. But where can I download
the DBD-MySQL package?
--Grace
ODELL, TODD E (SWBT) wrote:
Did you install the DBD-MySQL after the DBI install? You'd need to install
whatever DBD for db drivers you'd want to use through the DBI.
-Original Message-
From:
Hello.You can find it at http://search.cpan.org and search for MySQL there.
You can find pretty much any module for Perl here.
-Original Message-
From: Grace Tsai [mailto:gtsai;bnl.gov]
Sent: Wednesday, October 23, 2002 2:14 PM
To: ODELL, TODD E (SWBT)
Cc: [EMAIL PROTECTED]
Subject: Re:
Since my make perl could not find libperl.a, I re-attempted to install
DBD-Oracle-1.12 using the following stmt to create the Makefile
perl Makefile.PL PREFIX=/home/nbdipy2/perllib LIBPERL_A=libperl.so
I encountered the following error. My PATH is OK, LD_LIBRARY_PATH is OK,
LD_RUN_PATH is OK,
The uploaded file
DBD-Sybase-0.95.tar.gz
has entered CPAN as
file: $CPAN/authors/id/M/ME/MEWP/DBD-Sybase-0.95.tar.gz
size: 163549 bytes
md5: b3e905acf6fe894b59112d94a00e4c1f
This is a bug fix release - but it fixes a *lot* of bugs.
Please make sure that you test this version
Hi Jesse,
Yes, the client is unpatched so far.
Thanks for the hint.
We will try it out.
On Thu, 24 Oct 2002 00:36, Jesse, Rich wrote:
Hey Mike,
The OCI-21500 is definitely an Oracle problem. It's like the dreaded
ORA-600 error in that it should never happen. The main difference is that
RaiseError appears to be saved per statement handle and not changeable for
the execution of a given statement once the statement has been prepared.
Here's an example:
$dbh = DBI-connect(dbi:Oracle:$db, $user, $pw, {PrintError=0});
# before prepare, set RaiseError off
$dbh-{RaiseError} =
On Wed, Oct 23, 2002 at 08:05:42PM -0700, Mark Dedlow wrote:
RaiseError appears to be saved per statement handle and not changeable for
the execution of a given statement once the statement has been prepared.
Which is exactly as it's documented in the Fine Manual:
ATTRIBUTES COMMON TO ALL
Hi Folks.
Im seeing some nasty behaviour from DBD-Oracle with Oracle 9i that causes the
client to exit and core-dump with an Oracle internal error.
Below is a very simple program that illustrates the program. It connects to a
database (any Ora database will do, doesnt need any tables), then
On Tue, Oct 22, 2002 at 03:46:27PM -0400, Nallapati, Ram, CFCTR wrote:
PERL_DL_NONLAZY=1 /usr/local/bin/perl -Iblib/arch -Iblib/lib -I/usr/local/lib/pe
rl5/5.00503/sun4-solaris -I/usr/local/lib/perl5/5.00503 test.pl
test.pl
DBI test application $Revision: 10.3 $
opendir(./../../../..):
29 matches
Mail list logo
