Charles Lawrence ha scritto:
Gentlemen,
I'm hoping you can answer a question for me.
I am using an XP Pro platform accessing an MSSQL 2000 server. I use
ActivePerl 5.8.4 to access my database via ODBC. The latest versions of
the DBI and DBD-ODBC modules are installed. When I attempt to
Adamiec, Larry ha scritto:
I am trying to install Bundle::DBD::mysql on a Sun SPARC machine running
Solaris 9.
I am using CPAN (as root) to install
perl -MCPAN -e shell then install Bundle::DBD::mysql
Here is a portion of the output:
Checking if your kit is complete...
Looks good
Using DBI 1.47
I'm not familiar enough with trace output to know exactly what's
happening there, but I'm guessing that the UPDATE is the problem.
When you do an UPDATE, don't you *have* to have a WHERE
clause?
I see you're using ODBC - not sure if you've done this yet, or if you
have an ODBC client (or client
Hello
Has anyone tried the MySQL::Backup module with sucess?
I tried, but the export didn't go well.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John wrote:
Hello
Has anyone tried the MySQL::Backup module with sucess?
I tried, but the export didn't go well.
It wouldn't even build on my system and when I saw the version number I
just gave up and decided to wait until it has matured
From: Peter L. Berghold [EMAIL PROTECTED]
To: John [EMAIL PROTECTED]
Date: Friday, March 11, 2005, 5:57:53 PM
Subject: MySQL::Backup question
Friday, March 11, 2005, 5:57:53 PM, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John wrote:
Hello
Has anyone tried the
Ok. So I moved away from the UPDATE and now I am running a stored procedure.
When I look at the trace, the stored procedure runs exactly as expected,
however, it then runs a second time and screws things up. You can see on the
below trace what I mean. I believe this is what is clobbering the
First things first. When someone suggests something to you on this
list, especially
when they suggest it more than once, you should try it. I missed this
before, but I'm
remembering now an earlier suggestion by Michael Chase - when you
notice an error
in a dbi statement, print out $DBI::errstr
