[SOLVED] Update problem

[waynew]

  ??? Okay, I'm stumped on this one which means that it's probably something really simple after going wrong and that I need a second pair of eyes. Any help would be great.

 

I have a table that was set up as follows:

 

mysql_query("CREATE TABLE letter_template(
               
		   template_id int(2) not null,
		   primary key(template_id),
		   template_type varchar(20),
		   lost_tender text,
		   won_tender text,
		   pending_tender text
		   
		   )") or die("Problem");
		   
mysql_query("INSERT INTO letter_template(
                
			template_id, template_type, lost_tender, won_tender, pending_tender)

		 VALUES(1, 'Regular', 'Default', 'Default', 'Default')") or die(mysql_error);

 

Now, that worked fine and all fields were filled. The problem is on my update page:

 

if(isset($_POST['update'])){

$won = mysql_real_escape_string($_POST['won_tender']);
$lost = mysql_real_escape_string($_POST['lost_tender']);
$pending = mysql_real_escape_string($_POST['pending_tender']);
var_dump($_POST);



mysql_query("UPDATE letter_template
             SET won_tender = '$won',
		 SET lost_tender = '$lost',
		 SET pending_tender = '$pending'
		 WHERE template_type = 'Regular'
		 ") or die("Problem");

mysql_close();
}

 

As you can, I've done a var dump, which turned up fine. The problem is with the actual query update.

[trq]

Replace...

 

or die("Problem");

 

with....

 

or die(mysql_error());

 

and php will likely tell you what the problem is.

[waynew]

???

 

Use of undefined constant mysql_error - assumed 'mysql_error' in C:\Apache\htdocs\editlettercontent.php on line 37
mysql_error

[waynew]

Does anyone know what that error means?

[trq]

No, add...

 

or die(mysql_error());

 

Notice the () as in mysql_error() ?

[trq]

Does anyone know what that error means?

 

It means you didn't copy my code correctly.

[waynew]

Sorry, I was in a rush and didn't realise I hadn't put in the brackets

 

SET pending_ten' at line 3

[trq]

What error are you now getting?

[waynew]

Oh sorry. I fixed it. The problem was with the  SQL statement 

 

I used SET numerous times when I only needed to use it once. Don't know how I didn't realise that.

[trq]

Hehe, I don't know how I didn't see it either. These things happen huh.