On Fri, 08 Nov 2002 15:06:57 +, Simon Oliver wrote:
Jacqui Caren wrote:
On Fri, 08 Nov 2002 09:28:43 +, Simon Oliver wrote:
This is only true if RaiseError(s) is enabled and an exception was raised.
True.
My apologies for the delay in responding.
It is not true for an
On Wed, Nov 27, 2002 at 02:51:08PM -0500, Ronald J Kimball wrote:
But what's the query being sent to MySQL? Why does it think that the
value is the column?
I don't know how MySQL handles placeholders, so this is just a guess. It
may simply be interpolating the string 'nine' into the query
How can I execute a SQL Server stored proc from my Perl script? The Cheeta
book (DBD::ODBC Driver pg 296) suggests using the following ODBC escape
sequence:
{call procedure1_name}
Fine. But what's the rest of the syntax?
My platform is NT, ActivePerl 633...database is SQLServer2000.
TIA,
Hello,
I use Perl 5.6.0, DBI 1.30 and DBD-Oracle 1.12.
While checking the performance, my Oracle-Tools discovered, that the
Database does two prepares for every
execute.
My Perl-Code looks like this:
my $cur=$dbh-prepare($call);
die Prepare-Error: $DBI::err\n$call\n$DBI::errstr\n if
Class::DBI is a simple database-object mapping system. Simply point
it at your database, set up some classes to represent your tables,
tell it the relationships between your tables, and let it handle all
the 'simple' SQL for you (more complex queries can be written in SQL).
[See
Dears,
I am trying access system views form Oracle catalog with script below :
#!/usr/local/bin/perl -w
$ENV{ORACLE_HOME}=/oracle/8.1.7;
$ENV{NLS_LANG}= ;
$ENV{NLS_DATE_FORMAT}= ;
use DBI;
use CGI;
my $dbh = DBI-connect( dbi:Oracle:dbp2,sys,mypass);
my $sth = $dbh-prepare(select sid from
Hi ,
I am using DBI perl to connect to Oracle database. I am using qq against all
queries submitted through prepare statement.
I wanted to know if this is a good practice. Will this cause a problem in any
situation ?
Thanks and Regards,
Vikram
Brien Pirkle wrote:
How can I execute a SQL Server stored proc from my Perl script? The Cheeta
book (DBD::ODBC Driver pg 296) suggests using the following ODBC escape
sequence:
{call procedure1_name}
Fine. But what's the rest of the syntax?
From BOL:
The ODBC CALL escape sequence for
How can I execute a SQL Server stored proc from my Perl script?
The Cheeta
book (DBD::ODBC Driver pg 296) suggests using the following ODBC escape
sequence:
{call procedure1_name}
Fine. But what's the rest of the syntax?
Err, that is the syntax. If your procedure name is sp_foo,
W licie z czw, 28-11-2002, godz. 15:48, Vikram N pisze:
Hi ,
I am using DBI perl to connect to Oracle database. I am using qq against all
queries submitted through prepare statement.
I wanted to know if this is a good practice. Will this cause a problem in any
situation ?
I would prefer q
Jeff,
So, assuming sp_foo takes no paramters, my whole script could be:
#
use DBI;
my $dbh = DBI-connect('DBI:ODBC:OSTDB', 'user', 'password')
or die Couldn't connect to database: . DBI-errstr;
{call sp_foo}
#
Rgds,
Brien
Brien Pirkle wrote:
Jeff,
So, assuming sp_foo takes no paramters, my whole script could be:
#
use DBI;
my $dbh = DBI-connect('DBI:ODBC:OSTDB', 'user', 'password')
or die Couldn't connect to database: . DBI-errstr;
{call sp_foo}
#More like this:
my
Try $dbh-prepare($call, { ora_check_sql = 0 });
(The underlying issue is either an Oracle bug or that one of the
two parse steps counted isn't a real parse. DBD::Oracle does a
'describe only' execute at prepare() time and then a normal execute
when execute() is called. The execute() should not
Tim Bunce wrote:
On Tue, Nov 26, 2002 at 03:54:56PM -0600, Moritz von Schweinitz wrote:
Hi there,
this is kinda OT, since i fear it's more of a mysql than dbi issue, but
here goes...
the thing is that i have this long-running perlTk app. if i forcefully
bring my database-servre down (simply
I've encountered a similar problem with alarm().
Here's a piece of working production code that
succesfully uses alarm() with DBI.
my $dbh = '';
# database connection will cause perl to 'die'
# will just exit the eval block so we can check
You are attempting to login as SYSDBA.
The SYSTEM account cannot do that normally.
The requirements are:
remote_login_passwordfile = EXCLUSIVE
in the init.ora file.
create a password file with orpwd utility
grant SYSDBA to SYSTEM while logged into the
database via sqlplus as SYSDBA.
e.g.
The first parse is a 'hard' parse. This is the parse that
checks for existance of tables, privileges, and a bunch of
other stuff I probably don't know about.
The second parse is a 'soft' parse. It checks for existence
of the SQL in the Oracle library cache.
Oracle-Tools may not
17 matches
Mail list logo
