Re: DBI ORACLE ERROR

ERROR OCINlsEnvironmentVariableGet(OCI_NLS_CHARSET_ID) Check NLS You need to set some environment variables $ENV{ORACLE_HOME} = ...; $ENV{OCI_NLS_CHARSET_ID} = ...; From: Rakesh Ramachandran Sent: February 3, 2017 1:11 AM To: Deven

RE: [PATCH] Spelling fixes.

I had a change to go though it and it all looks ok. By the way 'dying' is correct the word you are thinking of is 'dyeing' English is such a silly language;) Cheers John Date: Tue, 11 Jun 2013 08:03:54 +0200 From: h.m.br...@xs4all.nl To: dbi-dev@perl.org Subject: Re: [PATCH] Spelling

RE: problem with bound columns and fetchall_arrayref with a slice

Hmm you always come up with the head scratchers, You are most likely on the right track. Somewhere way in the back of my mind I recall that the fetchall_arrayref was optimized for speed, and so the binding was left out but I am going back almost 10 years by memory. Do the other DBD do

RE: Building DBD::Oracle with one version but deploying with another

Should Allways work for 1 DB version forward and one back. So a 10 instantshould should work a 9,10 and 11 at least that is the theory. Oracle is a little unclear on what a Version is. What I usually do is complie with the instant client and depoly it with the compiled code. This is how

RE: Potential for new database driver

A pure perl version of the DBI already exists so I I take it you want to write a DBD::Blueprints? There are a number of pure perl DBD however I am not sure what Blueprints is??? Can you give us a link to it so I can at least see what you are writing a driver for?? Cheers John From:

RE: Handling idle database connections

you might wan to try visit_handles http://search.cpan.org/~timb/DBI-1.623/DBI.pm#visit_handles and visit_child_handles http://search.cpan.org/~timb/DBI-1.623/DBI.pm#visit_child_handles Send a code ref down the pipe and close the ones that have been idle for a while. Just a though.

RE: bind_param () - did something change?

I do not think so. That section of DBD::Oracle code does need some rework as it was written for Oracle 8. It should be updated to use the Oracle 10+ functionality for both select and updates. Alas one never seems to have any time work, (well finish actully) the work on this one. CheersJohn

RE: bind_param () - did something change?

Date: Mon, 28 Jan 2013 19:33:46 + From: martin.ev...@easysoft.com To: dbi-dev@perl.org Subject: Re: bind_param () - did something change? On 28/01/2013 19:03, John Scoles wrote: I do not think so. That section of DBD::Oracle code does need some rework as it was written

RE: Problem with procedures returning a SYS_REFCURSOR which is not open/executed - possible fixes

Date: Thu, 17 Jan 2013 13:48:15 + From: martin.ev...@easysoft.com To: c...@cam.ac.uk CC: dbi-dev@perl.org Subject: Re: Problem with procedures returning a SYS_REFCURSOR which is not open/executed - possible fixes On 17/01/13 12:26, Charles Jardine wrote: On 15/01/13 23:21,

RE: Problem with procedures returning a SYS_REFCURSOR which is not open/executed - possible fixes

Date: Thu, 17 Jan 2013 19:47:06 + From: martin.ev...@easysoft.com To: byter...@hotmail.com CC: c...@cam.ac.uk; dbi-dev@perl.org Subject: Re: Problem with procedures returning a SYS_REFCURSOR which is not open/executed - possible fixes On 17/01/2013 18:32, John Scoles wrote

RE: Problem with procedures returning a SYS_REFCURSOR which is not open/executed - possible fixes

Hmm you sure pick the head scratchers. My first thoughts where why whould you make such a procedure?? But then I relaisze it could have some use when prototying/develpopeing ect. Looking at 'DBD::Oracle attempts to describe statements which are initialized but not executed' We might be

RE: Oracle ping

Well I made that ping patch for DBIx::Connector a few months ago on one of my production boxes with no impact but then again I am not doing anything fancy (no rac raid etc). If it is critical to DBDx::Connector to ensure a query can be run then no, if you are going for 100% work alike

RE: Oracle ping

From: g...@turnstep.com To: dbi-dev@perl.org Subject: Re: Oracle ping Date: Mon, 5 Nov 2012 02:47:06 + -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Also by the time an application does execute some SQL, the the

RE: Oracle ping

Boy I think I really started something here. I just heard back from OIC connection over at Oracle and here is his two cents on the issue From an OCI point of view the OCIPing/OCIServerVersion calls are as good as it gets for basic aliveness of the connection. I'd never have thought they would

RE: dbi 1.622 with Turkish locale fails to connect to Oracle

You will have to give us the DBD::Oracle version as well. ORA-12514 is TNS:listener does not currently know of service requested in connect descriptor http://ora-12514.ora-code.com/ so I sort of suspect that you lintener and or service is not set up correctly to handle the language or the

RE: Patch proposal for leak in DBD::Oracle when calling 'execute_array' with UTF-8 NLS...

Hi guys had some time today to play again Seems we have one of three choices SvREFCNT_dec(tuples_utf8_av); as pathced or av_clear(tuples_utf8_av); at the send of the 'i' loop or sv_2mortal((SV*)tuples_utf8_av); at the begining I have tried them all and they all get rid of the

RE: Patch proposal for leak in DBD::Oracle when calling 'execute_array' with UTF-8 NLS...

I am sort of with Martin on this one as we would like to know why? At first glace decrementing the reference count like this would not seem to be a little overkill as tuples_utf8_av is created with newAV() which should take care of that for us. However looking a little deeper maybe we need to

RE: Patch proposal for leak in DBD::Oracle when calling 'execute_array' with UTF-8 NLS...

...@gmail.com To: byter...@hotmail.com CC: martin.ev...@easysoft.com; blan...@worldcom.ch; dbi-dev@perl.org On 9 October 2012 14:29, John Scoles byter...@hotmail.com wrote: I am sort of with Martin on this one as we would like to know why? At first glace decrementing the reference count like

RE: Patch proposal for leak in DBD::Oracle when calling 'execute_array' with UTF-8 NLS...

proposal for leak in DBD::Oracle when calling 'execute_array' with UTF-8 NLS... From: demer...@gmail.com To: byter...@hotmail.com CC: martin.ev...@easysoft.com; blan...@worldcom.ch; dbi-dev@perl.org On 9 October 2012 14:29, John Scoles byter...@hotmail.com wrote: I am sort of with Martin

RE: Problem with Oracle collections/objects

with SlJs here today Cheers John Scoles Date: Fri, 9 Dec 2011 14:01:43 + From: martin.ev...@easysoft.com To: dbi-dev@perl.org CC: dbi-us...@perl.org Subject: Problem with Oracle collections/objects Hi, If anyone is around who wrote or has worked on the object/collections

RE: Problem with Oracle collections/objects

till monday though swamped with SlJs here today Cheers John Scoles Date: Fri, 9 Dec 2011 14:01:43 + From: martin.ev...@easysoft.com To: dbi-dev@perl.org CC: dbi-us...@perl.org Subject: Problem with Oracle collections/objects Hi, If anyone is around who

DBD::Oracle Release Candidate 2

up a few of the tests. Thanks to H. Merijn Brand and Charles Jardine for those. Please enjoy. John Scoles

Re: DBD::Oracle Release Candidate 1

On 17/02/2011 7:34 AM, H.Merijn Brand wrote: On Wed, 16 Feb 2011 12:32:12 +0100, H.Merijn Brand h.m.br...@xs4all.nl wrote: http://www.pythian.com/news/wp-content/uploads/DBD-Oracle-1.28_RC_1.zip You need to work on longdouble support I guess Here's a patch to make the test PASS on all

Re: DBD::Oracle Release Candidate 1

On Wed, Feb 16, 2011 at 5:45 AM, Martin J. Evans martin.ev...@easysoft.com wrote: On 11/02/11 18:43, John Scoles wrote: Here is the latest and greatest DBD::Oracle for your programming pleasure. You can find the Zip file here a href=http://www.pythian.com/news/wp-content/uploads/DBD-Oracle

Re: Question about passing a stored procedure file to DBD-Oracle

ecord."END;" ); That might do the trick. Without seeing the original SQL it will be hard to give you a 100% answer. Cheers John Scoles I'm sorry in advance if this is not the correct forum/mechanism to ask this question - I have b

Re: more on execute_array not complying with the specification

On 02/02/2011 7:15 AM, Tim Bunce wrote: On Tue, Feb 01, 2011 at 09:02:26PM +, Martin J. Evans wrote: On 01/02/2011 20:50, Tim Bunce wrote: On Tue, Feb 01, 2011 at 10:58:14AM -0500, John Scoles wrote: My only concern is when it does error (no matter what the setting of AutoCommit) you

Re: more on execute_array not complying with the specification

, 2011 at 09:02:26PM +, Martin J. Evans wrote: On 01/02/2011 20:50, Tim Bunce wrote: On Tue, Feb 01, 2011 at 10:58:14AM -0500, John Scoles wrote: My only concern is when it does error (no matter what the setting of AutoCommit) you always get unef; Umm, yes. Returning undef (or an empty list

Re: more on execute_array not complying with the specification

On 01/02/2011 10:44 AM, Tim Bunce wrote: On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote: push @$tuple_status, [ $sth-err, $sth-errstr, $sth-state ]; so I guess the pod should say: If the execution of a tuple causes an error, then the corresponding status array

Re: more on execute_array not complying with the specification

On 01/02/2011 10:48 AM, Tim Bunce wrote: On Mon, Jan 31, 2011 at 08:39:40PM +, Martin J. Evans wrote: I imagine most DBDs [if not all] that implement execute_array [Just a reminder that drivers can opt to implement just execute_for_fetch() and use the DBI's default execute_array() method,

Re: more on execute_array not complying with the specification

One other thing I was picking up on is the case if you have autocommit on and RaiseError off I this case it if there was a an error while running in list mode it will allways return undef.  Where looking at the spec one might expect to see undef and XX which would be the # ot records effected?

Re: Clarification sought on execute_array

This behaviour is also inconsistent with versions of Oracle 11. Some patch sets show it other do not.I will have an answer for if later today Did you try it with the full 11 client. Cheers John On Fri, Jan 21, 2011 at 6:02 AM, Martin J. Evans martin.ev...@easysoft.comwrote: On 20/01/11

Re: $SIG{INT} tampering during DBI-connect on Oracle

On 20/01/2011 9:16 AM, Brian Phillips wrote: On Dec 1 2010, 9:59 am, sco...@pythian.com (John Scoles) wrote: It will be in 1.28 as 1.27 is reserved for now. Look for it in the next few weeks Any idea when 1.28 will be released? I want to have it out by the end of the Month. Remind me

Re: Clarification sought on execute_array

On 20/01/2011 12:20 PM, Martin J. Evans wrote: On 20/01/11 12:31, John Scoles wrote: On 19/01/2011 5:25 PM, Martin J. Evans wrote: Great stuff Martin I am sure we can clear this up. One thing I did notice was you never set the 'ora_array_chunk_size' which is defaulting to 1000 I wonder

Re: Clarification sought on execute_array

On 19/01/2011 6:47 AM, Tim Bunce wrote: As usual very sage advice Tim. I'm sorry to arrive here late. Seems I've been missing all the fun! Some observations: - I think it's reasonable for execute_array() and execute_for_fetch() to return an error (ie err() true and so trigger RaiseError

Re: Clarification sought on execute_array

On 17/01/2011 3:34 PM, Martin J. Evans wrote: There appear to be differences between DBDs which do not handle execute_array (so DBI does it for them) and DBDs which do handle execute_array (e.g., DBD::Oracle). The main ones discussed on #dbix-class which I investigated are whether the driver

Re: Clarification sought on execute_array

On 18/01/2011 7:52 AM, H.Merijn Brand wrote: On Tue, 18 Jan 2011 07:40:25 -0500, John Scolessco...@pythian.com wrote: On 17/01/2011 3:34 PM, Martin J. Evans wrote: There appear to be differences between DBDs which do not handle execute_array (so DBI does it for them) and DBDs which do

Re: Clarification sought on execute_array

On 18/01/2011 8:35 AM, Martin J. Evans wrote: John, I slightly reformatted you reply as you added comments on the end of lines I wrote which made it look like I said them. On 18/01/11 12:40, John Scoles wrote: On 17/01/2011 3:34 PM, Martin J. Evans wrote: There appear to be differences

Re: Clarification sought on execute_array

On 18/01/2011 9:47 AM, Martin J. Evans wrote: On 18/01/11 14:11, John Scoles wrote: On 18/01/2011 8:35 AM, Martin J. Evans wrote: John, I slightly reformatted you reply as you added comments on the end of lines I wrote which made it look like I said them. On 18/01/11 12:40, John Scoles

Re: Clarification sought on execute_array

On 18/01/2011 9:47 AM, Martin J. Evans wrote: Just as a Side note seems execute_array was added well after the first DBI spec was written. DBI 1.24,4th June 2002 seems to be the correct date rather a late addition. Cheers John On 18/01/11 14:11, John Scoles wrote: On 18/01/2011 8

Re: Clarification sought on execute_array

On 18/01/2011 9:47 AM, Martin J. Evans wrote: On 18/01/11 14:11, John Scoles wrote: On 18/01/2011 8:35 AM, Martin J. Evans wrote: John, I slightly reformatted you reply as you added comments on the end of lines I wrote which made it look like I said them. On 18/01/11 12:40, John Scoles

Re: DBD::Oracle - credentials

On 14/01/2011 9:30 AM, H.Merijn Brand wrote: Maybe this is a feature request, but if I have ORACLE_USERID=john/sekrit DBI_USER=pablo DBI_PASS=neruda I *do* expect that DBD::Oracle uses DBI_USER and DBI_PASS *instead of* the ORACLE_USERID. Anyone can come up with a good reason why

Re: DBD::Oracle - credentials

On 14/01/2011 10:21 AM, Martin J. Evans wrote: On 14/01/11 15:01, H.Merijn Brand wrote: On Fri, 14 Jan 2011 14:56:46 +, Martin J. Evans martin.ev...@easysoft.com wrote: On 14/01/11 14:30, H.Merijn Brand wrote: Maybe this is a feature request, but if I have ORACLE_USERID=john/sekrit

Re: DBD-Oracle stored proc with array bug

Ok I got it to work 100% with the test seems you gave a little too much SP You will find it in trunk of DBD::Oracle which is here http://svn.perl.org/modules/dbd-oracle/trunk Thanks again Cheers John Scoles On Tue, Dec 14, 2010 at 10:39 AM, Tim Oertel t...@samasher.com wrote: Hi, We

Re: DBD::Oracle 1.26 new_tablename / synonyms issue

I have applied this patch to trunk you can find it here http://svn.perl.org/modules/dbd-oracle/trunk It will be part of Release 1.28 sometime before the end of the month. Cheers John Scoles On Tue, Nov 16, 2010 at 10:28 AM, Jan Pazdziora jpz-p...@adelton.comwrote: Hello, The DBD::Oracle

ANNOUNCE: DBD::Oracle 1.27 Release Candidate 1

in a nutshell 1.27 is a single issue maintenance release. For those interested in the whole story you can have a look at this thread http://www.nntp.perl.org/group/perl.dbi.dev/2010/08/msg6217.html Any an all testing with differing Perls would be much appreciated Cheers John Scoles

Re: DBD-Oracle stored proc with array bug

should be out soon Cheers John Scoles On 14/12/2010 10:39 AM, Tim Oertel wrote: Hi, We were recently trying to pass an array to a stored procedure. It worked fine the first call, but subsequent calls were receiving the wrong array size, and with old array entries. After some investigation

Re: $SIG{INT} tampering during DBI-connect on Oracle

On 01/12/2010 9:22 AM, Brian Phillips wrote: On Nov 30, 8:37 am, sco...@pythian.com (John Scoles) wrote: Just wanting to make sure this doesn't get lost in the shuffle... Depends is it a specific OS patch for DBD::Oracle or a general one DBI? I am keeping an eye on it. I'm not sure why

Re: $SIG{INT} tampering during DBI-connect on Oracle

On 30/11/2010 10:28 AM, Tim Bunce wrote: On Mon, Nov 15, 2010 at 10:04:56AM -0800, Brian Phillips wrote: - DBD::Oracle::db::_login($dbh, $dbname, $user, $auth, $attr) - or return undef; +{ +my @local_signals = @{ $attr-{ora_local_signals} || [] }; +local

Re: $SIG{INT} tampering during DBI-connect on Oracle

On 15/11/2010 9:15 AM, Brian Phillips wrote: On Nov 9, 9:43 am, bpphill...@gmail.com (Brian Phillips) wrote: In my opinion, adding an option to change the current behavior is low risk and completely satisfactory for resolving my issue while leaving current behavior unchanged. If there are

ANNOUNCE DBD Oracle 1.27 Release Candidate 1

drivers that have been around for a while (like DBD::Oracle) may break!! Check out this thread http://www.nntp.perl.org/group/perl.dbi.dev/2010/08/msg6217.html for the long version I am announcing this on dbi-users as well to expand the group of people who may be using 5.13.3. Cheers John Scoles

Re: $SIG{INT} tampering during DBI-connect on Oracle

On 11/2/2010 2:49 PM, Brian Phillips wrote: Hello - I recently discovered that when we do a DBI-connect to an Oracle database, the process no longer responds to SIGINT signals. I'm not sure if it's something in DBD::Oracle (I can't find anything messing with $SIG{INT}) or something in the

Re: Perl 5.13.3+ MAY BREAK COMPILED DRIVERS

but it is much easier then trying to pick them all out yourself or by recompiling and fixing as you go. Cheers John Scoles file_PL_vars.pl Description: Perl program

Re: Perl 5.13.3+ MAY BREAK COMPILED DRIVERS - Please test DBI 1.613_71!

On 10/25/2010 10:33 AM, Tim Bunce wrote: On Mon, Aug 30, 2010 at 07:28:31AM -0400, John Scoles wrote: Tim Bunce wrote: Looks like DBD::Oracle as PERL_POLLUTE as well. Lucy!!! You have some renaming to do!!! A project of 1.26 perhaps As 5.13.x comes closer to being 5.14 this issue

Re: Perl 5.13.3+ MAY BREAK COMPILED DRIVERS - Please test DBI 1.613_71!

On 10/25/2010 1:42 PM, Martin J. Evans wrote: On 25/10/2010 18:04, John Scoles wrote: On 10/25/2010 10:33 AM, Tim Bunce wrote: On Mon, Aug 30, 2010 at 07:28:31AM -0400, John Scoles wrote: Tim Bunce wrote: Looks like DBD::Oracle as PERL_POLLUTE as well. Lucy!!! You have some renaming to do

Re: Perl 5.13.3+ MAY BREAK COMPILED DRIVERS - Please test DBI 1.613_71!

On 10/25/2010 1:52 PM, Martin J. Evans wrote: On 25/10/2010 18:57, John Scoles wrote: On 10/25/2010 1:42 PM, Martin J. Evans wrote: On 25/10/2010 18:04, John Scoles wrote: On 10/25/2010 10:33 AM, Tim Bunce wrote: On Mon, Aug 30, 2010 at 07:28:31AM -0400, John Scoles wrote: Tim Bunce wrote

ANNOUNCE: DBD::Oracle 1.25 Release Candidate 4

?? Please Enjoy John Scoles

Re: ANNOUNCE: DBD::Oracle 1.25 Release Candidate 4

wrote: On Wed, 15 Sep 2010 10:35:03 -0400, John Scoles sco...@pythian.com wrote: Ok here I am again for the fourth time :( You can find it here http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.25-RC4.tar Please use the correct extension: .tar.gz This one has some more

ANNOUNCE: DBD::Oracle 1.25 Release Candidate 3

it was a typo on my part. As well got rid of some harmless compiler warnings Cheers John Scoles -- The best compliment you could give Pythian for our service is a referral.

Re: Perl 5.13.3+ MAY BREAK COMPILED DRIVERS - Please test DBI 1.613_71!

Tim Bunce wrote: Looks like DBD::Oracle as PERL_POLLUTE as well. Lucy!!! You have some renaming to do!!! A project of 1.26 perhaps cheers John Short version: Please download build test *and install* DBI 1.613_71, then download build and test any compiled drivers you use to check they work

Re: ANNOUNCE: DBD::Oracle 1.25 Release Candidate

,is_initp );\ Hopefully that will get it Cheers John Scoles John Scoles wrote: Well story two of the 'two bit' version of DBD::Oracle 1.25 You can find release candidate 2 here http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.25-RC2.tar.gz This one has some minor changes from

Re: Please Test: AutoInactiveDestroy

David E. Wheeler wrote: Fellow DBIers, With a bit of help from me, Tim added a new feature to the DBI yesterday: AutoInactiveDestroy. I wrote the test for it. The test, however, forks. We need to make sure that it doesn't die an ugly death on systems without fork (and on Win32, where it's

Re: Please Test: AutoInactiveDestroy

/16destroy.t line 77 -- DBI::END ($@: , $!: ) DESTROY in DBD::Test::db ('DBI::db=HASH(0x202027c)') [] FETCH in DBD::Test::db ('DBI::db=HASH(0x202027c)' 'Active') [] FETCH= 0 at ./t/16destroy.t line 77 t/zvp_16destroy.t .. Failed 2/20 subtests On Jul 27, 2010, at 5:01 AM, John

Re: Please Test: AutoInactiveDestroy

David E. Wheeler wrote: now we are getting t/zvp_16destroy.t(Wstat: 0 Tests: 18 Failed: 0) Parse errors: Bad plan. You planned 20 tests but ran 18. t/zvxgp_16destroy.t (Wstat: 0 Tests: 18 Failed: 0) Parse errors: Bad plan. You planned 20 tests but ran 18. Files=171, Tests=6280,

Re: Please Test: AutoInactiveDestroy

') [] FETCH= 0 at ./t/16destroy.t line 79 On Jul 27, 2010, at 11:17 AM, John Scoles wrote: David E. Wheeler wrote: now we are getting t/zvp_16destroy.t(Wstat: 0 Tests: 18 Failed: 0) Parse errors: Bad plan. You planned 20 tests but ran 18. t/zvxgp_16destroy.t (Wstat: 0 Tests

ANNOUNCE: DBD::Oracle 1.25 Release Candidate

. and hopefully I got rid of the warning error in the .xs file for OCILobLocatorIsInit_log_stat And of course the usual bunch of POD changes. Cheers John Scoles -- New! Learn why how to love your data with Pythian's new webinar series. Topics, details register: http://www.pythian.com/webinars

Re: ANNOUNCE: DBD::Oracle 1.25 Release Candidate

Make sure you double check the MANIFEST if that is important for you system. I have yet to make sure it is 100% complete yet. Jens Rehsack wrote: 2010/7/23 John Scoles sco...@pythian.com: Well story two of the 'two bit' version of DBD::Oracle 1.25 You can find release candidate 2 here

Re: ANNOUNCE: DBD::Oracle 1.25 Release Candidate 1

, 2010-07-16 at 13:04 -0400, John Scoles wrote: John Scoles wrote: Nobody wants to play with my new toy? I will, waiting for our dba to setup the DRCP for me. :( Well it is finally here the 'two bit' version of DBD::Oracle 1.25 You can find the release candidate here http

Re: ANNOUNCE: DBD::Oracle 1.25 Release Candidate 1

John Scoles wrote: Nobody wants to play with my new toy? :( Well it is finally here the 'two bit' version of DBD::Oracle 1.25 You can find the release candidate here http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.25-RC1.tar.gz Any and all testing will be most welcome! The big

ANNOUNCE: DBD::Oracle 1.25 Release Candidate 1

Pool) if you happen to be using 11g or later As well 'get_info' has been greatly expanded Plus the the usual hodgepodge of bug fixes detailed below Added support for the OCIPing by John Scoles Spell checked the pod (the first time in a while me thinks) updated the todo By John Scoles Added

Re: DBD::Oracle DRCP_1.25

names rather than POOL. as well I made ORA_DRCP_CLASS an optional value. Some users my not want to use it. Thanks again John Scoles On Wed, Jul 7, 2010 at 4:34 PM, luben karavelov lu...@unixsol.org wrote: As I have promissed, here comes the documentation patch. I am not native speeker, so

Re: Minor issue with ping

The way Ping works is different is depending on the version of DBD::Oracle you are using. Which version of DBD::Oracle are you using?? cheers John Scoles On Thu, Jun 17, 2010 at 2:34 PM, Thomas M. Payerle paye...@umd.edu wrote: Hi, My colleagues and I encountered a problem in some code

Re: Spelling

H.Merijn Brand wrote: For my own projects (which includes two DBD's), I have been working on spell-check issues. I'm not born in an English-speaking country, nor was I raised in one, so I make errors. Probably quite a few. spell-checkers help a lot, but most work on en_US, not en_EN, and I try

Re: DBD::Oracle 11gr2 ORA-38909

Had a quick look at it today give it a try agian but this time make sure you have autocommit off AutoCommit=1 on the connection method cheers On Fri, May 21, 2010 at 11:20 AM, John Scoles sco...@pythian.com wrote: Ok I guess it is back to square 1 on this. Unfortunetly no time to look

Re: DBD::Oracle 11gr2 ORA-38909

: John Scoles wrote: Ok I have patched up a solution I think will work across the board and you can find it here http://svn.perl.org/modules/dbd-oracle/branches/oci_batch here are the details ora_oci_batch For 11g users you may encounter an error while using the execute_array

Re: DBD::Oracle 11gr2 ORA-38909

to the 'OCI_BATCH_MODE' problem I will add it in as like id did for ora_ncs_buff_mtpl so one can set it at the ENV, connect and statement level so I can cover of any situation that may require a solution Look for it as ora_oci_batch and ORA_DBD_OCI_BATCH for the env Cheers john Scoles -- See Pythian's

Re: DBD::Oracle 11gr2 ORA-38909

this value. It can also be set as an attribute on both the Connect and Prepare. Unfortunately I can't test it (do not have an 11g box yet) so It will stay in the above branch until it is tested hopefully by you Scott Cheers John Scoles -- See Pythian's Alex Gorbachev, co-author of Expert Oracle

Re: DBI and do

be meaningless, something like a sentence with only punctuation. cheers John Scoles With best regards, Thomas Knoerl Siemens AG Siemens IT Solutions and Services SIS IT SM CP Wuerzburger Str. 121 90766 Fuerth, Germany Tel.: +49 (911) 978-3034 Fax: +49 (911) 978-2037 Mobile: +49 (1522) 2795353

Re: Comments on this patch for dbms_output_get() ?

simple enough I will put it in the 1.25 release I created this patch because of this issue (which we have run into), == Parameter Description line Returns a single line of buffered information,

Re: ANNOUNCE: DBD::Oracle 1.24 Release Candidate 5

Great looks like a release on Monday cheers John Scoles wrote: Horray. Just one more thing has come up in like the last 15min can you redo your the make test with the following file http://svn.perl.org/modules/dbd-oracle/trunk/ocitrace.h It is a trivial change but just want to make

ANNOUNCE: DBD::Oracle 1.24 Release Candidate 5

Well here comes the big #5 It can be found at the usual place http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.24-RC5.tar This time round was a patch to fix a patch for some warnings that was causing a seg-fault on some 32 bit boxes Cheers and thanks for all the testing John

ANNOUNCE: DBD::Oracle 1.24 Release Candidate 4

Well here comes #4 It can be found at the usual place http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.24-RC4.tar This time round I added a little patch from Charles Jardine fro objects and some fixes for warnings I have changed the ora_ncs_buff_mtpl default value back to 4 so

Re: ANNOUNCE: DBD::Oracle 1.24 Release Candidate 3

and send me the results I will have something more to go on. Look for another RC in the next day or two. Cheers Jardine wrote: On 14/01/10 12:19, Charles Jardine wrote: On 12/01/10 12:07, John Scoles wrote: Ok third time is a Charm The Third RC of the beer edition of DBD::Oracle 1.24 can be found

ANNOUNCE: DBD::Oracle 1.24 Release Candidate 2

Ok third time is a Charm The Third RC of the beer edition of DBD::Oracle 1.24 can be found at http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.24-RC3.tar This round has a few little patches from Martin Evans on it. Please test and enjoy Cheers John Scoles

ANNOUNCE: DBD::Oracle 1.24 Release Candidate 2

Well here it is the second crack at 1.24 Beer version of DBD::ORACLE You can find the release candidate here http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.24-RC2.tar this time out I have hopefully fixed most of the warnings I have also updated the pod to explain what

Re: DBD-Oracle-1.23 Makefile.PL patch

Of you could give it a try on 64 bit power solaris it you want to tug all of your hair out. H.Merijn Brand wrote: On Fri, 27 Nov 2009 10:41:19 -0400, Ralph Doncaster ralphdoncas...@gmail.com wrote: On 11/27/09, H.Merijn Brand h.m.br...@xs4all.nl wrote: On Fri, 27 Nov 2009 10:21:05

Re: DBD::Oracle - is ora_lob_read mangling BLOB data?

Can you tell us which version of DBD::Oracle you are using. There is quite a differance between versions when it comes to UTF8 handling. Milo van der Leij wrote: I am in the progress of changing some code that uses DBD::Oracle to use the documented ora_lob_read function instead of the

ANNOUNCE: DBD::Oracle 1.23 Release Candidate 3

-oracle/trunk/dbd_Oracle_123_RC3.tar Cheers John Scoles

ANNOUNCE: DBD::Oracle 1.23 Release Candidate 1

of a statement handle. and I also added a patch from Tomas Pokorny for extended Object support Here is the complete change list Fix in case there may be a bug in 11 where the OCI_ATTR_DATA_SIZE my return 0 which should never happen, John Scoles Fix on the Makefile.PL for a possible sql bug in IC from

Re: ANNOUNCE: DBD::Oracle 1.23 Release Candidate 1

Ok I will try and fix it up Andy Hassall wrote: On Mon, February 16, 2009 5:33 pm, John Scoles wrote: Well here it is the long awaited 1.23 http://www.youtube.com/watch?v=67khDZ0P7Xo or the Sesame Street http://en.wikipedia.org/wiki/Sesame_Street version of DBD::ORACLE You can find

Re: ANNOUNCE: DBD::Oracle 1.23 Release Candidate 1

Seem my first Tar was bad please try this one http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.23-RC2.tar Andy Hassall wrote: On Mon, February 16, 2009 5:33 pm, John Scoles wrote: Well here it is the long awaited 1.23 http://www.youtube.com/watch?v=67khDZ0P7Xo or the Sesame

Re: enhancement: DBD::Oracle and OCI_ATTR_STMT_TYPE

Well would not be hard to do as we already have char * oci_stmt_type_name(int stmt_type) { dTHX; SV *sv; switch (stmt_type) { case OCI_STMT_SELECT: return SELECT; case OCI_STMT_UPDATE: return UPDATE; case OCI_STMT_DELETE: return DELETE; case OCI_STMT_INSERT: return INSERT; case OCI_STMT_CREATE:

Re: (Fwd) noitify author of DBD::Oracle

You can ignore it for now. It has nothing to do with the functionality of DBD::Oracle it is a CPAN file that I was mistakenly put into the manifest. cheers John Scoles Tim Bunce wrote: - Forwarded message from Chuck Pareto [EMAIL PROTECTED] - Subject: noitify author of DBD::Oracle

Re: ANNOUNCE: DBD::Oracle 1.22 Release Candidate 3

H.Merijn Brand wrote: On Wed, 30 Jul 2008 18:00:52 -0400, John Scoles [EMAIL PROTECTED] wrote: Ok hot off the press RC3 A few more minor fixed but a last minute patch for ora_lob_chunk_size function It can be found in the usual spot http://svn.perl.org/modules/dbd-oracle/trunk/DBD

Re: Taking trace () to the next level ...

H.Merijn Brand wrote: On Tue, 02 Sep 2008 19:03:26 +0100, Martin J. Evans [EMAIL PROTECTED] wrote: H.Merijn Brand wrote: On Tue, 2 Sep 2008 11:15:20 +0100, Tim Bunce [EMAIL PROTECTED] wrote: On Mon, Sep 01, 2008 at 05:01:40PM -0700, Jonathan Leffler wrote: On

Re: Taking trace () to the next level ...

of debugging (DBI and DBD) 2) Flags that that can turn debugging off or on for a specific action -debug_select -debug_commit -debug_connect -debug_oracle ??? cheers John Scoles

ANNOUNCE: DBD::Oracle 1.22 Release Candidate 3

Ok hot off the press RC3 A few more minor fixed but a last minute patch for ora_lob_chunk_size function It can be found in the usual spot http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.22-RC3.tar Cheers and thanks for all the help guys John Scoles

ANNOUNCE: DBD::Oracle 1.22 Release Candidate 2

Ok hot off the press RC2 I have fixed as much as I can of the different compiler warnings hopefully this will be a little better. You can find the RC here http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.22-RC2.tar Cheers and thanks for all the help guys John Scoles

Re: ANNOUNCE: DBD::Oracle 1.22 Release Candidate 2

Gisle Aas wrote: On Jul 28, 2008, at 18:06, John Scoles wrote: Ok hot off the press RC2 I have fixed as much as I can of the different compiler warnings hopefully this will be a little better. You can find the RC here http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.22-RC2

Re: ANNOUNCE: DBD::Oracle 1.22 Release Candidate 2

Is it bad to install the mkta.pl file? or is it just harmless junk that does not need to be there? Gisle Aas wrote: Can I suggest that you apply the following patch? The goal is to prevent the installation of the lib/DBD/mkta.pl file. --Gisle Index: Makefile.PL --- Makefile.PL.~1~ Mon

ANNOUNCE: DBD::Oracle 1.22 Release Candidate 1

in this version Update to connection part of POB from John Scoles Fix to test suite to bring it up to standard from Martin Evans Fix for memory hemorrhage in bind_param_inout_array found by Ricky Egeland, Fix by John Scoles Fix for a typo in oracle.xs from Milo van der Leij Fix for bugs on SPs with Lobs

  1   2   >