Re: Looking for help with odd DBD::Oracle::db prepare behavior

2007-04-03 Thread Adriano Ferreira
nts before sticking them into SQL (as this is a good chance for an injection attack). For instance, you may split the argument and then sanitize the parts to make sure they contain only digits: my @args = split '-', $arg; s/[^\d]// for @args; -Original Message- From: Adriano Ferre

Re: Looking for help with odd DBD::Oracle::db prepare behavior

2007-04-02 Thread Adriano Ferreira
On 4/2/07, Nelli, Joseph R. Jr. <[EMAIL PROTECTED]> wrote: I've been using DBD::Oracle::db from my Perl scripts for some time and have had no problems. Today, I've started to get some odd behavior. I create a delete string and attempt to prepare it. I get a ORA-00936 error meesage. I don't know w

Fwd: [perl #40331] Installation of DBD 1.18

2006-09-13 Thread Adriano Ferreira
-- Forwarded message -- From: Juan Carlos GarcĂ­a via RT <[EMAIL PROTECTED]> Date: Sep 13, 2006 4:47 AM Subject: [perl #40331] Installation of DBD 1.18 To: "of perl Ticket #40331\"" <"AdminCc> http://rt.perl.org/rt3/Ticket/Display.html?id=40331 > Hi. I'm triying to install the la

Re: Apostrophie problem(s)

2006-09-10 Thread Adriano Ferreira
7;'Jones'", while a MySQL handle would answer "'O\\'Jones'".) Third, you probably will do better by using SQL statements with placeholders that take care of all these subtleties for you. Regards, Adriano Ferreira On 9/9/06, Owen <[EMAIL PROTECTED]>

Re: Is it a bug in DBD::SQLite? [cpan #15166]

2005-10-21 Thread Adriano Ferreira
. On 10/20/05, Adriano Ferreira <[EMAIL PROTECTED]> wrote: > While developing, I gave DBD::SQLite a bad SQL statement like "select > 'eek" (quoted string not terminated). It worked and gave a weird > answer. Is that something I should be expecting? Some oddity of &g

Is it a bug in DBD::SQLite?

2005-10-20 Thread Adriano Ferreira
While developing, I gave DBD::SQLite a bad SQL statement like "select 'eek" (quoted string not terminated). It worked and gave a weird answer. Is that something I should be expecting? Some oddity of SQLite? The following test script was run #!/usr/bin/perl use DBI; use DBD

Re: DBD::Oracle and ErrCount

2005-10-14 Thread Adriano Ferreira
On 10/14/05, Tim Bunce <[EMAIL PROTECTED]> wrote: > It does use set_err (and the XS equiv DBIh_SET_ERR_*). Did you try it? Yes. I am not sure I don't understand when ErrCount should be incremented or if my installation has problems. But it works in general. I got the following output ---

DBD::Oracle and ErrCount

2005-10-13 Thread Adriano Ferreira
DBI docs say: The ErrCount attribute was added in DBI 1.41. Older drivers may not have been updated to use set_err() to record errors and so this attribute may not be incremented when using them. DBD::Oracle 1.16 is one of those drivers that are not using set_err() yet? Regards, Adr

Re: upgrading dbi

2005-05-18 Thread Adriano Ferreira
On 5/17/05, Jonathan Leffler <[EMAIL PROTECTED]> wrote: > And Perl 5.006001 is hardly the most recent version of Perl. I think April would prefer a-step-by-step approach. Upgrading the DBI can be enough for while. Upgrading Perl would mean recompiling all Perl modules with XS parts which are not b

Re: Calling Stored Procedure using REF CURSORS

2005-04-18 Thread Adriano Ferreira
On 4/18/05, Denesa K Shaw <[EMAIL PROTECTED]> wrote: > DBI::db=HASH(0x2035aef0)->disconnect invalidates 1 active statement handle > (either destroy > statement handles or call finish on them before disconnecting) Well, you need "either destroy statement handles or call finish on them before discon

Re: Sending Mail

2005-03-25 Thread Adriano Ferreira
>my $sth = $dbh->prepare("SELECT email_address FROM users WHERE >email_address='[EMAIL PROTECTED]'") >The above line did not work, so the address was not found, guess who forgot >to escape the @ !! If you were using the recommended pragma use warnings; at the beginning of the script (or runnin

Re: Strange DBI Bug

2005-03-23 Thread Adriano Ferreira
On Wed, 23 Mar 2005 19:56:48 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > This statement ... > causes a deadlock. But accidently, we found that this one ... > works! Maybe it's not a DBI or DBD::Oracle problem. How about this issue if the statement is executed via other tools