RE: UPDATE Statement Problem...

2002-04-02 Thread Moritz von Schweinitz
ore interesting problems by now ;-) M. > -Original Message- > From: NIPP, SCOTT V (SBCSI) [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 02, 2002 12:07 PM > To: '[EMAIL PROTECTED]' > Subject: RE: UPDATE Statement Problem... > > > IT'S ALIVE

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
--Original Message- From: NIPP, SCOTT V (SBCSI) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 11:47 AM To: 'Michael Ragsdale'; '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: RE: UPDATE Statement Problem... OK. Sorry for my being stupid. Everyon

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
02, 2002 11:15 AM To: NIPP, SCOTT V (SBCSI); '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: RE: UPDATE Statement Problem... At 12:01 PM 4/2/2002, NIPP, SCOTT V (SBCSI) wrote: > New problem now. I appear have resolved my earlier problems. The >final i

RE: UPDATE Statement Problem...

2002-04-02 Thread Jeff Seger
dbh->do(qq{UPDATE systems SET $set WHERE 'Name = $name'}); > > Not sure what is wrong now though. :( > > -Original Message- > From: NIPP, SCOTT V (SBCSI) > [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 02, 2002 10:46 AM > To: '[EMAIL P

Re: UPDATE Statement Problem...

2002-04-02 Thread Ronald J Kimball
On Tue, Apr 02, 2002 at 11:01:41AM -0600, NIPP, SCOTT V (SBCSI) wrote: > New problem now. I appear have resolved my earlier problems. The > final issue appears to have been that the SQL statement was interpreting the > WHERE clause as having multiple arguments. Quoting the where clause se

RE: UPDATE Statement Problem...

2002-04-02 Thread Michael Ragsdale
At 12:01 PM 4/2/2002, NIPP, SCOTT V (SBCSI) wrote: > New problem now. I appear have resolved my earlier problems. The >final issue appears to have been that the SQL statement was interpreting the >WHERE clause as having multiple arguments. Quoting the where clause seems >to have resolve

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
il 02, 2002 10:46 AM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: RE: UPDATE Statement Problem... I actually have that covered, I think. The variable $set actually expands to something like ip='192.168.0.1' , speed='450' , etc. This portion

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
if $set; $set .= $key . "=\'$$key\'"; } } Thanks again. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 10:40 AM To: NIPP, SCOTT V (SBCSI) Subject: RE: UPDATE Statement Problem... THe problem with the update

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
SCOTT V (SBCSI) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 10:28 AM To: 'Michael Ragsdale'; 'Tielman J de Villiers' Cc: '[EMAIL PROTECTED]' Subject: RE: UPDATE Statement Problem... A bit more information... Here is the error message from the Perl scrip

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
sage- From: NIPP, SCOTT V (SBCSI) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 10:20 AM To: 'Michael Ragsdale'; 'Tielman J de Villiers' Cc: '[EMAIL PROTECTED]' Subject: RE: UPDATE Statement Problem... Wow!!! This is one awesome mailing list. I r

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
). Once I get that part figured out and going, I think I can home in on the problem rather quickly. Then I will just have to port this portion of code from my laptop to my Unix platform. Thanks again for all of the helpful suggestions. Almost everything you guys have responded with so far

RE: UPDATE Statement Problem...

2002-04-02 Thread Gordon.Rhea
Now that I read this more carefully I have some more thoughts on this. You need to do some error checking when you call execute. Simply checking the value of $test won't do it as $test is set to a statement handle by prepare. The line "if($test)" should always be true as $test will always be non

RE: UPDATE Statement Problem...

2002-04-02 Thread Michael Ragsdale
At 10:50 AM 4/2/2002, NIPP, SCOTT V (SBCSI) wrote: > I added a COMMIT immediately after the UPDATE, and still have the >same problem. Below is exactly what I added, with the lines immediately >before and after. > > $dbh->do(q{UPDATE systems SET = $set WHERE Name = $name LIMIT 1}

RE: UPDATE Statement Problem...

2002-04-02 Thread Gordon.Rhea
ielman J de Villiers' Cc: '[EMAIL PROTECTED]' Subject: RE: UPDATE Statement Problem... I added a COMMIT immediately after the UPDATE, and still have the same problem. Below is exactly what I added, with the lines immediately before and after. $dbh->do(q{UPDATE sys

RE: UPDATE Statement Problem...

2002-04-02 Thread timothy . helck
Scott, The first step in debugging a problem like this is to have your perl script print out the Update statement and then cut and paste that statement into your usual database frontend and run it. (In oracle it sould be sql*plus, I don't know what it is in MySQL). This will tell you if there's a

RE: UPDATE Statement Problem...

2002-04-02 Thread NIPP, SCOTT V (SBCSI)
;); #Just added!!! } else { -Original Message- From: Tielman J de Villiers [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 9:39 AM To: NIPP, SCOTT V (SBCSI) Cc: '[EMAIL PROTECTED]' Subject: RE: UPDATE Statement Problem... Check how you connect -- if Autocommit is not o

RE: UPDATE Statement Problem...

2002-04-02 Thread Tielman J de Villiers
Check how you connect -- if Autocommit is not on, then you need to commit after you update Tielman J de Villiers BondNet Pty Ltd -Original Message- From: NIPP, SCOTT V (SBCSI) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 5:40 PM To: '[EMAIL PROTECTED]' Subject: UPDATE Statem