(mysql_error()); doesn't print the error

polarexpress

i'm encountering a very strange issue.

(mysql_error()); doesn't print the error in the following syntax although it can't update the values into database on form action.

$insert = "INSERT into `table` (`name`,`email`) VALUES ('$name','$email')";
mysql_query($insert,$link) or die(mysql_error());

here $link variable refers to database connection as it does commonly.

i never encountered such a strange issue.

any idea, why? thanks,

bradgrafelman

Store the value returned by [man]mysql_query/man into a variable and use [man]var_dump/man to determine exactly what that return value was. I'm guessing it wasn't boolean FALSE. Show us the output from the var_dump().

Also, have you tried echo'ing out the SQL query to see if it looks like what you expected? I only ask since you haven't shown us where you define the variables $name and $email.

EDIT: Forgot to mention.. note that the entire [man]mysql[/man] extension has been outdated for quite some time and is deprecated by the PHP developers. Thus, you shouldn't be using it. See [man]mysqlinfo.api.choosing[/man] for more info.

polarexpress

if i use anything except (mysql_error()); the form is submitted properly but the values actually aren't updated to the database. it's applicable to var_dump() too. it seems that the data are being updated to any other 2nd database reserved by my joker web host.

bradgrafelman

polarexpress;11015491 wrote:
the values actually aren't updated to the database.

Refer to the second paragraph in my post above.

polarexpress;11015491 wrote:
it's applicable to var_dump() too.

What does "it's applicable" mean? What did the var_dump() reveal as far as what the return value of mysql_query() really is?

polarexpress

when i use mysql_query($insert,$link) or die(mysql_error()); the page dies to a blank page on form submission without any mysql_error, when i use mysql_query($insert,$link) or (mysql_error()); the form is submitted properly without updating the values to database and when i use $output=mysql_query($insert,$link); var_dump($output); the form is submitted properly without updating the values to database. none of the functions returns any mysql_error.

bradgrafelman

Did you read my post above? You still haven't done this (as far as I can tell):

bradgrafelman;11015485 wrote:
Also, have you tried echo'ing out the SQL query to see if it looks like what you expected?

Also, can you show us where you define $name and $email?

polarexpress

$name & $email were defined properly. echoing query doesn't make any difference. (mysql_error()); doesn't print an error on error, isn't it funny?

bradgrafelman

polarexpress;11015503 wrote:
$name & $email were defined properly.

...so you claim. However, you're also having issues, which is why I'm not really going to take your word on it. 😉

Why can't you simply copy and paste the exact PHP statements where you define those variables and let us determine if they were "defined properly" ?

polarexpress;11015503 wrote:
echoing query doesn't make any difference.

Uh, yeah it does. It shows you the exact SQL query that is being sent to your SQL server, meaning you can copy-and-paste it here for us to examine. What other "difference" were you expecting it to make?

QUOTE=polarexpress;11015503; doesn't print an error on error, isn't it funny?[/QUOTE][/quote]No, because it's very possible there is no error occurring. Fore example, if the variables $name and $email didn't exist or weren't defined correctly, you'd be telling the SQL server to insert a row with no data. It will happily do so - thus, there is no error.

polarexpress

an incorrect database field name in the insert statement caused the problem. shouldn't mysql error function returns an error in this case? that was a severe mistake.

traq

polarexpress;11015517 wrote:
an incorrect database field name in the insert statement caused the problem. shouldn't mysql error function returns an error in this case? that was a severe mistake.

maybe something is returned. throughout this thread, you've been describing your code in two different ways:

polarexpress;11015495 wrote:
when i use mysql_query($insert,$link) or die(mysql_error());
[...]
when i use mysql_query($insert,$link) or (mysql_error());

which is your actual code? if you wrote

mysql_query($insert,$link) or (mysql_error());

nothing would be printed (because you didn't instruct php to print anything).

Weedpacket

The [font=monospace]... or die(mysql_error());[/font] idiom is pretty weak anyway. It may be sufficient in development, or as part of a command-line utility, but on a web site in the real world it's less than useless; the only people who would want to see that sort of behaviour are the sort of people you wouldn't want to be seeing it.

polarexpress

i used mysql_query($insert,$link) or (mysql_error()); to check the output only. mysql_query($insert,$link) or die(mysql_error()); i used to print the output and in the most cases it return errors

polarexpress

traq;11015535 wrote:
maybe something is returned. throughout this thread, you've been describing your code in two different ways:which is your actual code? if you wrote
mysql_query($insert,$link) or (mysql_error());
nothing would be printed (because you didn't instruct php to print anything).

i used mysql_query($insert,$link) or (mysql_error()); to check the output only. mysql_query($insert,$link) or die(mysql_error()); i used to print the output and in the most cases it return errors

traq

polarexpress;11015545 wrote:
i used mysql_query($insert,$link) or (mysql_error()); to check the output only.

I'm not sure what you mean by that. Check it how?

if [font=monospace]mysql_query()[/font] returns false, then [font=monospace]mysql_error()[/font] will most likely return true [truthy] - so, your check will (almost?) always return true.