Hi,
I am using Perl DBI/DBD for Oracle. I have a lot of PL/SQL, and I can't
find any mention of whether or not Perl DBI can receive Oracle PL/SQL
structures (PL/SQL tables of type RECORD) back from a call to a PL/SQL
call.
TYPE t_task_cmd_list IS TABLE OF VARCHAR2(1000)
FUNCTION
Hi Reiner,
when i execute a query against the data that contains the swedish
character
å i get a ? returned instead.
unfortunately, there are more places where something can get wrong :-(
1. What is your database character set?
(select * from nls_database_parameters where parameter =
On Tue, 10 Feb 2004 18:10:42 -0500, Andrew Pimlott wrote:
Is there any way to prevent the following from warning Issuing
rollback() for database handle being DESTROY'd without explicit
disconnect().?
use DBI;
my $dbh = DBI-connect('dbi:Pg:dbname=...', undef, undef,
{
On Tue, Feb 10, 2004 at 11:20:42PM -, Andy Hassall wrote:
Just to pre-empt the probably soon to be frequently-asked question, here's
one data point: DBD::Oracle 1.15 appears to work OK on Oracle 10.1.0.2 on
Linux.
Great, thanks.
t/ph_typeok 11/19 Placeholder behaviour for ora_type=1
On Wed, Feb 11, 2004 at 09:42:00AM +0100, Bart Lateur wrote:
On Tue, 10 Feb 2004 18:10:42 -0500, Andrew Pimlott wrote:
Is there any way to prevent the following from warning Issuing
rollback() for database handle being DESTROY'd without explicit
disconnect().?
use DBI;
my $dbh
thanks to all who have answered. it was indeed the NLS_LANG variable that
i needed to set in my linux shell.
now things work like they should.
once again, thanks.
Just to pre-empt the probably soon to be frequently-asked question, here's one
data point: DBD::Oracle 1.15 appears to work OK on Oracle 10.1.0.2 on Linux.
[EMAIL PROTECTED]:~/src/DBD-Oracle-1.15-andyh$ make test
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0,
Tim Bunce wrote:
On Thu, Feb 05, 2004 at 10:50:46AM +, Charles Jardine wrote:
If not, would it be useful if I re-worked the patch for
version 1.15.
That would be great. Thanks.
A re-worked patch to make placeholder binding in DBD::Oracle
case insensitive is attached.
--
Charles Jardine -
On Wed, Feb 11, 2004 at 09:35:59AM +, Tim Bunce wrote:
For mod_perl you can register a suitable callback.
I am using mod_perl, and that's what I mean about having to jump through
hooks (probably not that difficult in this case) to suppress the
warning.
The warning as it's a significant
On Wed, Feb 11, 2004 at 12:00:28PM +, Charles Jardine wrote:
Tim Bunce wrote:
On Thu, Feb 05, 2004 at 10:50:46AM +, Charles Jardine wrote:
If not, would it be useful if I re-worked the patch for
version 1.15.
That would be great. Thanks.
A re-worked patch to make placeholder
On Wed, Feb 11, 2004 at 08:15:12AM -0500, Andrew Pimlott wrote:
p.s. The plan is to have a way for a driver to indicate if it's in a
transaction and, for drivers that can, use that to skip the warning.
Ok, so you'd like to issue the warning in the dangerous case only, but
DBI doesn't
I generally only add something to the DBI when the DBI can 'fake it'
for drivers that can't do it themselves. In this case the DBI will
count execute()/do() calls and reset the counter on
commit()/rollback().
Then the counter can be used to control the warning for drivers that
can't tell if
It's an excellent idea for the DBI to fake certain things when it makes
sense. But transaction control is not one of them. Transaction control
is appropriately handled only by an application. In other words, only an
application knows when it should or should not commit or rollback.
Additionally,
My app uses the following statements to try and call a stored procedure running on SQL
Server 7:
#Execute stored procedure sp_FEFC_BudgetedFinancialStatement to organize data
for report
my $shelby3_sth = $shelby3_db-prepare(EXEC
sp_FEFC_BudgetedFinancialStatement ?, ?, ?;);
My app uses the following statements to try and call a stored
procedure running on SQL Server 7:
#Execute stored procedure
sp_FEFC_BudgetedFinancialStatement to organize data for report
my $shelby3_sth = $shelby3_db-prepare(EXEC
sp_FEFC_BudgetedFinancialStatement ?, ?,
On Wed, Feb 11, 2004 at 04:24:31PM +, Tim Bunce wrote:
On Wed, Feb 11, 2004 at 08:15:12AM -0500, Andrew Pimlott wrote:
Ok, so you'd like to issue the warning in the dangerous case only, but
DBI doesn't have the necessary information. That seems like a rather
conspicuous flaw in the
On Wed, Feb 11, 2004 at 11:43:49AM -0600, Jeff Holt wrote:
It's an excellent idea for the DBI to fake certain things when it makes
sense. But transaction control is not one of them. Transaction control
is appropriately handled only by an application. In other words, only an
application knows
On Wed, Feb 11, 2004 at 09:41:08AM -0800, Henri Asseily wrote:
I generally only add something to the DBI when the DBI can 'fake it'
for drivers that can't do it themselves. In this case the DBI will
count execute()/do() calls and reset the counter on
commit()/rollback().
Then the counter
Actually, there at at least two things wrong with letting a dbms perform
session garbage collection.
The first is assuming a definition for session garbage collection. The
second is assuming that the dbms will always keep that definition in
spite of its evolution.
Garbage collection is defined
Have you tried without proxy server?
It works if I don't use the proxy server as long as I bind the param and then pass all
three variables in $sth-execute().
Do you have output of what value is actually being bound, on both the server side and
the client side?
I'm not sure how to get this
I am attempting to install DBD-mysql-2.9003 on a Solaris 2.8 machine.
The DBI is 1.40. It runs the perl Makefile.PL (I use the cflags, libs,
testuser, testpassword and testhost options) amd make without any errors
but when I run the make test, the test are failing. Here is the feedback
from make
Have you tried without proxy server?
It works if I don't use the proxy server as long as I bind
the param and then pass all three variables in $sth-execute().
That's probably because you are binding with SQL_VARCHAR and DBD::ODBC tries
to detect which type the column is and handle the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there any way to prevent the following from warning Issuing
rollback() for database handle being DESTROY'd without explicit
disconnect().?
...
I'm using DBI 1.40 and DBD::Pg 1.31 on Debian testing.
I played with this a bit today and am
23 matches
Mail list logo
