Re: Memoizing non-place-holding sql statements to place-holding

2005-08-22 Thread Jonathan Leffler
On 8/22/05, John Siracusa <[EMAIL PROTECTED]> wrote: > > On 8/21/05 10:38 PM, [EMAIL PROTECTED] wrote: > > I'm using DBD:DB2. > > Maybe quatation (') rwapping data must be dropped, and > > "CURRENT TIMESTAMP" keyword will be treated. > > > > my @new_values = (); > > my @place_holders = > > map { >

RE: Memoizing non-place-holding sql statements to place-holding

2005-08-22 Thread h-taguchi
Thank you so much. I was checking UDFs. Now SQL::Statement has become my tool. Thank you again. Regards, Hirosi Taguti [EMAIL PROTECTED] > >INSERT INTO MyTbl (col1,record_ts,col2) > > VALUES (7,CURRENT TIMESTAMP,'o''brian') }; > > > That calls for a combination of SQL::Statement and your

Re: Memoizing non-place-holding sql statements to place-holding

2005-08-22 Thread Jeff Zucker
[EMAIL PROTECTED] wrote: >I'm dealing with: > >INSERT INTO MyTbl (col1,record_ts,col2) > VALUES (7,CURRENT TIMESTAMP,'o''brian') }; > That calls for a combination of SQL::Statement and your method. You have to trick SQL::Statement into thinking that "CURRENT TIMESTAMP" is a string (because

RE: Memoizing non-place-holding sql statements to place-holding

2005-08-22 Thread h-taguchi
> >>> my @new_values = (); > >>> my @place_holders = > >>> map { > >>> if (/^CURRENT TIMESTAMP$/) { > >>> $_; > >>> } else { > >>> push @new_values => $_; > >>> "?"; > >>> } > >>> } @args > >>> ; > >> > > > >SQL::Statement can do this? > > > Yes. The snippet I sent before will automatically turn #

Re: DBD Oracle column type

2005-08-22 Thread Tim Bunce
Ah. You're trying to bind a placeholder as a BFILE. That's not supported yet. I've no idea what's required, possibly not much. Patches welcome. Tim. On Mon, Aug 22, 2005 at 10:36:42AM -0500, Paul Dyer wrote: > Hi and thanks for the feedback, > > ORA_BFILE doesn't seem to be defined in DBD::Oracl

Re: Memoizing non-place-holding sql statements to place-holding

2005-08-22 Thread Jeff Zucker
[EMAIL PROTECTED] wrote: >>> my @new_values = (); >>> my @place_holders = >>> map { >>> if (/^CURRENT TIMESTAMP$/) { >>> $_; >>> } else { >>> push @new_values => $_; >>> "?"; >>> } >>> } @args >>> ; >> > >SQL::Statement can do this? > Yes. The snippet I sent before will automatically turn #1 into

RE: DBI for Win2000 installation

2005-08-22 Thread CAMPBELL, BRIAN D (BRIAN)
To use PPM to download DBI, I also had to set my http_proxy. But I may have also had to change the repositories that were initially configured in PPM. So if you still can't connect you may want to try that too. Use the PPM rep command to view and change repositories. Refer to the Activestate docs:

Re: DBD Oracle column type

2005-08-22 Thread Paul Dyer
Hi and thanks for the feedback, ORA_BFILE doesn't seem to be defined in DBD::Oracle. I get this error when I use it: Bareword "ORA_BFILE" not allowed while "strict subs" in use or this error when I turn off strict: Argument "ORA_BFILE" isn't numeric in subroutine entry at ./purge_image

RE: FW: Failed DBD Oracle 1.16 make on Perl 5.8.6, DBI 1.48,Oracle 9.2.0.6, Solaris 8.

2005-08-22 Thread Reidy, Ron
Did you read the README* files and follow the directions? Look for the line "*** *BEFORE* BUILDING, TESTING AND INSTALLING DBD::Oracle:" in the README file at the top of the distribution. Pay specific attention to this section: Make sure Oracle is working and you can use Oracle commands

Re: DBD Oracle column type

2005-08-22 Thread Tim Bunce
On Sun, Aug 21, 2005 at 05:39:39PM -0500, Paul Dyer wrote: > Hi Tim, > > Thanks for the reply. I am using Perl 5.8, Perl-DBI 1.32, DBD::Oracle > 1.16, and RedHat Linux 2.4.21-32. > > I will take another look at what could be wrong. It helps to know that > BFILE is included. I noticed that DB

RE: FW: Failed DBD Oracle 1.16 make on Perl 5.8.6, DBI 1.48,Oracle 9.2.0.6, Solaris 8.

2005-08-22 Thread Chiang, William T
Do we need to install Oracle ProC first before we install DBD-Oracle-1.16? I am not sure they post to the dbi-users. From: Scott T. Hildreth [mailto:[EMAIL PROTECTED] Sent: Fri 8/19/2005 4:11 PM To: Chiang, William T Cc: dbi-users@perl.org Subject: Re: FW: Failed

RE: Memoizing non-place-holding sql statements to place-holding

2005-08-22 Thread h-taguchi
> > my @new_values = (); > > my @place_holders = > > map { > > if (/^CURRENT TIMESTAMP$/) { > > $_; > > } else { > > push @new_values => $_; > > "?"; > > } > > } @args > > ; ... > It's a bit of a pain, but until DBD::Informix becomes "smart" > enough to > detec

Re: Memoizing non-place-holding sql statements to place-holding

2005-08-22 Thread John Siracusa
On 8/21/05 10:38 PM, [EMAIL PROTECTED] wrote: > I'm using DBD:DB2. > Maybe quatation (') rwapping data must be dropped, and > "CURRENT TIMESTAMP" keyword will be treated. > > my @new_values = (); > my @place_holders = > map { > if (/^CURRENT TIMESTAMP$/) { > $_; > } else { >

AW: DBI for Win2000 installation

2005-08-22 Thread Mickautsch, Alfred
Hello, if you are behind a firewall you must set http_proxy to your proxy. set http_proxy=http://yourproxy.yourdomain.de:yourproxyport Servus -- Alfred -- Alfred Mickautsch Schuler Business Solutions AG Karl-Berner-Str. 4 D-72285 Pfalzgrafenweiler tel:+49 (0)74 45 830-184 fax:+49 (0)74

DBI for Win2000 installation

2005-08-22 Thread Christian Stalp
Hello, I installed ActivPerl 5.8.7 on Windows2000. While installation of DBI I got these errors dumped: Error: No valid repositories: Error: 500 Can't connect to ppm.ActiveState.com:80 (connect: Unknown error) Error: 500 Can't connect to ppm.ActiveState.com:80 (connect: Unknown error) Does anybody

Re: DBD Oracle column type

2005-08-22 Thread Tim Bunce
On Sat, Aug 20, 2005 at 12:31:47AM -0500, Paul Dyer wrote: > > The problem is that my column type is NOT correctly BLOB. ora_type CLOB and > BLOB are defined as integer values (112 and 113). I am using type BFILE, > which is 114. When I use the integer 114 as the type, I get the error > stating