From: "Michael A Mayo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject:Re: executing atomic transactions in DBI
Date sent: Mon, 7 May 2001 14:27:40 -0400
Michael,
> > if the commit() is placed here, won't it be always execute
From: Neil Lunn <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject:RE: executing atomic transactions in DBI
Date sent: Tue, 8 May 2001 13:38:33 +1000
Neil,
meanwhile I have performed some experiments and found out that I
misunde
On 7 May 2001, at 12:30, Ronald J Kimball wrote:
> On Mon, May 07, 2001 at 06:22:01PM +0200, Philip Newton wrote:
> > But you get warnings on $dbh->disconnect if you don't finish all your
> > statement handles. At least that's why I always try to remember it.
>
> But if you select all the rows
> -Original Message-
> From: Shah, Deepak K [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 08, 2001 10:32 AM
> To: '[EMAIL PROTECTED]'
> Subject: database query fails when run with Perl
>
>
> Hello,
>
> We are running a query against an Oracle database using Perl.
> This query has
>
Should this really be discussed off the list? Abolutely not.
Ilya, your connect string in this script uses PrintError, as you knowingly
mention yourself. I thought that this was made very clear in the docs.
>From the fine Manual:
""PrintError"" (boolean, inherited)
This attribute can be use
> Sorry to interfere so late in this thread, but
>
> if the commit() is placed here, won't it be always executed, because
> there are no die statements which stop code execution upon errors
> before ? Shouldn't committing be made dependent of the value of $@
> like
>
> if ($@) {
> warn
What kind of problems were you having? I am just wondering because of our
prior discussions. There is a new DBD::Excel available (released few days
ago partly due to our heated discussion on this). If you ever try that
driver let us know if that solved any problems.
Ilya Sterin
-Original
I found, over time, that DBD::ODBC had problems with Excel. I would save
the Excel sheet as .csv and used DBD::CSV, instead. My use was a one way
conversion/update of Oracle from the spread sheets. I made a macro for the
data entry people to update the .csv file without having to think too
hard
First you are providing an arg to your execute, though I don't see you using
any placeholder. See perldoc for prepare() and execute() statements, so I
don't even know how you are able to run the script. Do you have RaiseError
=> 1 and PrintError => 1. Also what is the error message you are gett
Hi!
(Sorry for delay!)
The fragment below shows how I made data dump of the table, containing
binary data.
Then, using editor (Ultraedit) I compared the content of the output file
with the file created by mysqldump.
The difference is that the DBI->quote() did not escape some characters that
were
David Sevier writes:
> When done using DBD:ODBC through the proxy, it works fine. But with
> DBD:Sybase, the metadata returned for items of type Float are a problem.
> They always come back with a Pecision of 8 and a Scale that is empty (null).
A Float doesn't have any scale, and precision
Jacob Kuntz writes:
> In the cheetah book's section on DBD::Sybase, there is a URL for a patch for
> MS SQL that allows connects from Sybase clietns, but the link now appears to
> be dead. Does anyone have an updated link? Is the patch still necisary with
> FreeTDS 0.51?
The patch was only ne
- Original Message -
From: "Stephen M. Ford" <[EMAIL PROTECTED]>
To: "Sterin, Ilya" <[EMAIL PROTECTED]>
Subject: RE: :Pg again
> I changed the $dbh line to
>
> my $dbh =
DBI->connect("dbi:Pg:dbname=tracker;host=bullwinkle.eng.auburn.edu;port=5432
;","","");
>
> and added a dbh->trace(4) an
In the cheetah book's section on DBD::Sybase, there is a URL for a patch for
MS SQL that allows connects from Sybase clietns, but the link now appears to
be dead. Does anyone have an updated link? Is the patch still necisary with
FreeTDS 0.51?
--
Jacob Kuntz
Technology Director
The Real Estate C
Hi all!
Thanks for the quick (and helpful) responses last time!
I have anohter problem with DBD:Sybase. I've got a simple program that pulls
the metadata for a column:
sub GetMetaData
{
### Routine to get MetaData on a specific column
my $connection = shift;
my $username= shift;
my $passw
How about applying the corrections and suggestions provided earlier on this
list?
The "DBI.errstr" all by itself should get you a warning if you add 'use
strict;' to the script and '-w' to the '#!' line. There are almost
certainly other problems that those two additions would expose too.
--
Mac
It's a known problem between DBI 1.15 and DBD::Oracle's return cursor
handling. Drop back to DBI 1.14 and re-build DBD::Oracle.
--
Mac :})
** I normally forward private database questions to the DBI mail lists. **
Give a hobbit a fish and he'll eat fish for a day.
Give a hobbit a ring and he'll e
As the subject says getting core's in make test when trying to build
DBD-Oracle in perl 5.6.1. This is on a Compaq Alpha with Oracle 8.1.6.
Has anyone seen this work before? Any ideas on what could be wrong? It
was coreing on test 55 which I think is:
ok(0, $parent->bind_param(":p1", "V%"));
- Original Message -
From: "Bodo Eing" <[EMAIL PROTECTED]>
Subject: RE: executing atomic transactions in DBI>
> if the commit() is placed here, won't it be always executed, because
> there are no die statements which stop code execution upon errors
> before ? Shouldn't committing be made d
- Original Message -
From: "Stephen M. Ford" <[EMAIL PROTECTED]>
Subject: dbd::Pg again
> Can someone tell me what is wrong with this statement?
> $dbh = DBI->connect("dbi:Pg:tracker;host=bullwinkle;port=5432;","","");
> DBI->connect(tracker;host=131.204.12.48;port=5432;) failed: 1 at
./tr
I changed the $dbh line to
my $dbh =
DBI->connect("dbi:Pg:dbname=tracker;host=bullwinkle.eng.auburn.edu;port=5432;","","");
and added a dbh->trace(4) and got the following output. It appears to fail around the
connect with DBI.pm.
DBI 1.14-nothread dispatch trace level set to 4
Note:
On Mon, 7 May 2001, Stephen M. Ford wrote:
> Can someone tell me what is wrong with this statement?
>
> $dbh = DBI->connect("dbi:Pg:tracker;host=bullwinkle;port=5432;","","");
>
> DBI->connect(tracker;host=131.204.12.48;port=5432;) failed: 1 at ./tracker2.pl line
>16
It should be "dbi:Pg:dbnam
On Mon, May 07, 2001 at 06:22:01PM +0200, Philip Newton wrote:
> On 7 May 2001, at 1:12, Thomas A. Lowery wrote:
>
> > On Mon, May 07, 2001 at 09:51:39AM +0530, [EMAIL PROTECTED] wrote:
> > > > $rs->finish();
> > Only really needed if not selecting all the rows for the
>
Right, but you never checked if execute() failed with || die() or set the
RaiseError and PrintError to 1. So it never failed. By defauld the error
checking is not turned on, though you must specifically set {RaiseError =>
1, PrintError => 1} or use || die().
Ilya Sterin
-Original Message--
On 7 May 2001, at 1:12, Thomas A. Lowery wrote:
> On Mon, May 07, 2001 at 09:51:39AM +0530, [EMAIL PROTECTED] wrote:
> > > $rs->finish();
> Only really needed if not selecting all the rows for the
> statement.
But you get warnings on $dbh->disconnect if you don'
Here is part of the code:
{
if ($operacion eq "INGRESAR"){
$SQL1="SELECT ID FROM OPERADORES WHERE ID=?";
$buscar_id_operador = $dbh->prepare($SQL1) || die "Couldn't prepare
statement: " . $dbh->errstr;
$buscar_id_operador->execute($codigo);
@data1=$buscar_id_operador->fetchrow_array();
$buscar_
Use trace() to find out the exact reason for connect failing.
Ilya Sterin
-Original Message-
From: Stephen M. Ford
To: [EMAIL PROTECTED]
Sent: 05/07/2001 9:58 AM
Subject: dbd::Pg again
Can someone tell me what is wrong with this statement?
$dbh = DBI->connect("dbi:Pg:tracker;host=bullw
Can someone tell me what is wrong with this statement?
$dbh = DBI->connect("dbi:Pg:tracker;host=bullwinkle;port=5432;","","");
DBI->connect(tracker;host=131.204.12.48;port=5432;) failed: 1 at ./tracker2.pl line 16
Thanks,
Stephen
Let's try some shorter code first so it is easier to find the error:
#!c:/perl/bin/perl
use CGI qw(:standard);
use DBI;
$ query= new CGI();
@tryarr=(3456,3457,3489,2723);
my $dbh= DBI->connect('DBI:ODBC:SCART','team','team') or
die " Sorry could not connect". DBI.errstr;
print $query->header(
We need a little bit more code than this. What do you mean by $@ not being
understood? Are you using eval{}? Is you script failing within eval{}?
Are you setting RaiseError => 1 or using || die()?
Ilya Sterin
-Original Message-
From: Julio Santiago
To: [EMAIL PROTECTED]
Sent: 05/07/20
Hi There!!!
All my perl scripts are runnig ok, they execute all the transactions almost
perfectly until an error occurs during insertions or updates.
I am using the $@ to handle the errors returned by the database but it seems
that the $@ value is not being understood.
I use the following pie
>
> The problem: I've written a web site thinking that DBI and DBD were
> standard. Now I find they are not and the ISP will not load them for
> everyone to use :(. This is my first venture into PERL so I don't know
> what I'm doing.
>
> I need to load the DBD, DBI and CSV drivers into the web
Randal, we'll discuss off list since I totally agree that this (rumor??) can
get out of hand. The script provided is supposed to fail when the query
does not execute due to mispelled table name, but it rather prints the error
message (as it suppost to) but then proceeds to print the rest of the f
* Judge Dredd ([EMAIL PROTECTED]) [010507 10:30]:
> Hash: SHA1
>
> Hello to all
>
> I don't know if this should go to dbi-users but neither i know of a
> specific list to post it. My problem is that i wan to access a
> netscape directory server running in a solaris box using perl as in a
> win20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello to all
I don't know if this should go to dbi-users but neither i know of a
specific list to post it. My problem is that i wan to access a
netscape directory server running in a solaris box using perl as in a
win2000 box. I do not know what are
Jim Lambert writes:
> I need to implement something like Oracle sequences in Sybase. I
> found a good article at:
>
> http://www.isug.com/Sybase_FAQ/ASE/section6.2.html
>
> There's only one problem. All the sequence implementations listed
> don't deal with long transactions. Usi
> "Ilya" == Sterin, Ilya <[EMAIL PROTECTED]> writes:
Ilya> Not sure what you consider a rumor, I just simply stated having
Ilya> a problem with it before and that in my experience I always
Ilya> check for return value, due to either the query failing and/or
Ilya> executing without failing, bu
Not sure what you consider a rumor, I just simply stated having a problem
with it before and that in my experience I always check for return value,
due to either the query failing and/or executing without failing, but still
producing an unexpected result.
By implying that the trasaction does not
Attached is a script that prints an error but keeps processing, though never
actually failing? It actually failed on the one and only query since the
table name was mispelled, but proceeded to print the rest of the form.
Ilya Sterin
DBI 1.14
DBD::Oracle 1.06
OS Sun Solaris SunOS 5.7
-
Dear Paul & Yannis:
I apologize for not sending the code. I thought it might be something simple
that had been seen before and would go away with something like:
$sth->{problem_go_away} = 1;
I guess not! Anyhow, when I cut my program down to send you something
digestible I found that the pr
On Fri, May 04, 2001 at 03:26:40PM -0700, SELVARAJAN,DANESH K (Non-HP-PaloAlto,ex1)
wrote:
> Hi Tim,
>
> $sth->finish
>
> This Indicates that no more data will be fetched from this statement before
> it is either prepared again or destroyed and to allow the server to free up
I need to implement something like Oracle sequences in Sybase. I
found a good article at:
http://www.isug.com/Sybase_FAQ/ASE/section6.2.html
There's only one problem. All the sequence implementations listed
don't deal with long transactions. Using these implementations I
would get dead
hello
i'm using DBD::ODBC v0.28 with Solid EE v3.51. for some reason the result
set field values get mixed up with earlier field values. for example:
select TABLE_NAME, COLUMN_NAME, DATA_TYPE from COLUMNS
where table_schema = 'TEST1' and table_name in ('US
In article <[EMAIL PROTECTED]>, Sterin,
Ilya <[EMAIL PROTECTED]> writes
>Well if you would of read the Readme and any other install files like you
>are suppost to when installing anything, that it would of walked you through
>a proper install procedure. You can't just install the .pm files. DBI
44 matches
Mail list logo
