Okay, I don't really consider myself a novice when it comes to PHP and MySQL, but it has been over a year since I messed with it. The problem I am having is getting my form data stored in a MySQL table. The data is being sent properly, but, for some reason, only 3 fields will go into the table. Here is my very basic code:

<?php
                         
$connect = mysql_connect("localhost", "$user", "$password");
mysql_select_db("database", $connect);
              
mysql_query("INSERT INTO new (email, name, yourclass, mspec) 
VALUES('$_POST[email]','$_POST[name]','$_POST[yourclass]','$_POST[mspec]')");
              
echo "Done!";
?>

Now, if I remove the 'mspec' variable, the email, name, and yourclass variable will be placed in my table like I want them. However, as soon as I add the mspec variable...nothing. I need to add 13 fields into a table and it is seriously starting to tick me off that something that should have taken 10 minutes is taking me 2 hours. Can anyone spot something that I am just doing wrong?

Your query is right... As long as your db table have the schema that correspond to it.
Are you sure you have a field named "mspec" in your table, and that this field is in a text or varchar datatype ?

Wow, I am such an idiot. My form has it listed as mspec, but my database has it as m_spec. I can't believe I wasted all that time for this. Thanks, dude.

And since I did about the same thing last month, allow me to add that Myfield and myfield are not the same either.


And I knew better.

This isn't related to your question, but I noticed that you've left yourself wide open to sql injection. You should validate and sanitize your post data before inserting it into the database.

http://us2.php.net/manual/en/functio...ape-string.php

Hi.
Please refer to the url below:
http://www.infinite-fire.net/tutoria...mysql-database
I wish it will be helpful.
Regards,
freezea.

Originally Posted by colbyt

And since I did about the same thing last month, allow me to add that Myfield and myfield are not the same either.


And I knew better.

It's even worse than that.
Mysql using files for the table storage, and the convention being that the table name IS the file name, the tables names follow the OS case sensitivity.
Meaning that the tables names are case sensitive on unixes/bsd boxes, but case insensitive on windows.
And what is true for the tables is true for the field, in my memory.
The fields are case insensitive on windows, but case sensitive on linux.

I found out the hard way (ie, rewriting case sensitive query from a dev that did everything on windows when installing on a linux server)

And what is true for the tables is true for the field, in my memory

Your memory serves you correctly.

Your memory serves you correctly.

I cannot tell you, as a DBA, how much I hate literally working with mysql.
I seriously don't understand how it could gain so much traction.
Sigh...