I wanted to build an awesome place for people to discuss module specific issues, but I don't have any more time for this, and there are much better places to discuss Perl-related issues. I'd recommend asking your question on Stack Overflow or on Perl Monks.
If you are looking for a Perl tutorial or Perl-related news, I hope these links will serve you well.
Posted on 2008-11-27 08:27:45-08 by iboritchev
a problem with ora type for date
I work with perl 5.8.8. I have a problem when I execute a stored procedure. I pass the parameters as a hash. One of output parameters is of type "DATE". If I write:
my_par_type_date => { length => 20, type => &ORA_DATE }
or
my_par_type_date => { length => 7, type => &ORA_DATE }
I get: ora_type 12 not supported by DBD::Oracle If I write:
my_par_type_date => => { length => 20, type => &ORA_VARCHAR2 }
I get (by Data::Dumper) the values of parameters not corresponding to the keys (the mess concerns the other parameters, not my_par_type_date). Finally,if I write
my_par_type_date => { length => 20, type => 12 } all the output parameters are undef and one of them (not my_par_type_date) is not viewed by Dumper.
Direct Responses: 9449 | Write a response
Posted on 2008-11-28 10:46:00-08 by byterock in response to 9443
Re: a problem with ora type for date
To start most date functions are dependant on NLS settings.
to properly debug this I will need to know the version of DBD::Oracle you are using as well I need some test code that will recreate it.
Nothing fancy is needed just a simple schema with some perl code that recreats the problem
By they way noone but me actully look at this list
You would be much better off posting this at
http://www.nntp.perl.org/group/perl.dbi.users/
or raise a RT ticket at
http://rt.cpan.org/Dist/Display.html?Queue=DBD-Oracle
Direct Responses: Write a response