SQL Queries & Form Posting Help!!!

Thatsquality

Basically I have a form that posts by the name 'group' to a PHP page that is designed to accept both posts and Gets (.php?group=") but the variable from the post is acting differently.

<?php
$username="Something";
$password="Somethingelse";
$database="Product";

mysql_connect('localhost',$username,$password); 
@mysql_select_db($database) or die( "Unable to select database");

if (empty($_POST))
{
if (empty($_GET['group']))
{
$PID = "WM";
}
else
{
$PID = $_GET['group'];
}
}
else
{
$PID = $_POST["group"];
}
$result2 = mysql_query("SELECT * from groupy where ID='$PID'");
$Conversion = mysql_fetch_row ($result2);
?>

Basically, I can get the $PID variable to be set to the exact same value by Posting or using the .php?= method. Even though the variable, at least appears, to be the same value either way, the query functions differently depending on the origin of the $PID variable. In both cases $result2 is a valid query (returning Resource id #3) but only in the case of using the (.php?=) format of setting the $PID variable does the $Conversion variable get accurately set by the mysql_fetch_row function. If the $PID variable is set by posting and retrieved by the $_Post() function, the mysql_fetch_row function returns an empty array, which frankly is depressing on my part.

So there are no errors, but the variable is acting in two different ways via the SQL fetch row and that doesn't make sense! Is there something I don't understand about the $_POST function???

nemonoman

Please echo your query

echo "SELECT * from groupy where ID='$PID'";

Using both get and post methods. Let us see the actual query; and the associated results. I've got a guess at what's happening, but I'd like to see the query first before I make a complete fool of myself.

I hate these kind of bugs, don't you? They drive you nuts.

Thatsquality

I ran the code with the echo in there with both the post and the get and this is what I echoed:

Post:
SELECT * from groupy where ID='WM'

Get:
SELECT * from groupy where ID='WM'

<b>However</b> and this is where I am even more puzzled today, although I would understand how this is somehow my fault, I ran the print_r() function on the conversion variable this morning and, out of nowhere, the Post and Get functions are returning a varibale that is equally handled by the SQL queries. So basically, without changing anything critical I know about, the problem is solved, but I would love to hear input on what may have been happening or what I may have done to fix/break the issue.

Thanks

nemonoman

Your story suggests that your browser was using a cached version of the form rather than a fresh, fixed version. You probably had fixed the code several times over but were still using a cached copy.l

This happens all the time to me with GD Micro$oft GDF Internet Explorer. Even if you set your preferences not to cache, or send 'don't cache' headers, etc., etc., Micro$oft appears to have a Higher Vision of what to keep cached.

One of my last bug fix strategies is clearing all cached files, and clearing cookies too (since I keep some data in cookies). Just yesterday this disposed of a bug that I couldn't figure out where the hell it came from. Turned out I'd fixed it, but GDF IE hadn't yet digested the fact.

I still can't figure out how I displayed a form with PARTIALLY new data(!!), but it was doing so until I cleared the cache, and everything showed up new and correct.

GO figure.

mystrymaster

simply hold ctrl while you are refreshing a page and hit will go get a new version regardless of your preferences.