On Tue, Nov 02, 2004 at 04:48:07PM -0500, Jason White wrote: > On Nov 2, 2004, at 3:23 PM, Tim Bunce wrote: > >On Tue, Nov 02, 2004 at 02:56:10PM -0500, Jason White wrote: > >>> > >>>FYI DBD::Oracle 1.06 is over 4 years old. > >> > >>Yes, was aware of that to my own frustration. Was able to work with > >>sysadmin to get upt to 1.14 at least ... an advance of 2.5 years at > >>least. > > > >So does DBD::Oracle 1.14 pass its test suite? > > Initially it skipped most tests as the host, username etc. were/are > empty. The initial test passed and then it skipped a number of tests > ... and failed (I assumed) due to the lack of that information so went > ahead and did the make install. > > After a few more rounds with the make test, I'm convinced that my > environment vars aren't correct for the test ... TWO_TASK should be set > to the remote host correct?
Yes. And set ORACLE_USERID. Can't test much if it can't connect. See the README. > >[Could you build 1.16 locally, but not install it, for testing?] > > Cannot get 1.15 or 1.16 (fails on dbdimp.o) to make. We have a separate > install of perl and the script needs to use that instance of perl, so > we have to build with that install. Make sure the perl you're using is the first perl in your PATH. > >> fbh 1: 'STS_ISS' NULLable, otype 2-> 5, dbsize 22/134, p3.s0 > > I changed the query back to select * instead of select STS_ISS ... and > it shows that it is changing the type wholesale, not just on the number > field. Apparently it doesn't matter on the other ones in terms of the > data since they are type VARCHAR2 > ... > fbh 7: 'FIRST_NAME' NO null , otype 1-> 5, dbsize 40/41, p40.s0 > fbh 8: 'STS_ISS' NULLable, otype 2-> 5, dbsize 22/134, p3.s0 > fbh 9: 'XLIST' NULLable, otype 1-> 5, dbsize 8/9, p8.s0 > > So ... what might cause this or how might types be strictly defined? That's entirely normal and expected behaviour. > >>1 <- fetch= [ '.' ] row1 at sisQuery.pl line 27 > > > >Something is clearly very wrong, but I find it hard to believe that > >DBD::Oracle code is the cause - given so many people using it without > >problems. > > I believe you and asked this question fully suspecting it to be > something on my part. Always encouraging to hear the > > > I've never seen a problem like this reported. > ;) > > BTW ... congrats on your developer of the year award! Thanks. Tim.
