I have this problem with php and mysql where I query a table a database and it works fine, but then i go and query another table in the same database and it won't let me (or returns nothing). On top of that, the "or die (mysql_error())" function won't return anything but it is dying after that statement. In the past, i have moved around this problem by putting everything in it's own database. Since that is, overall, a terrible idea, I would like to know how to fix this problem weather it be a setting i need to change or a piece of code i need to include.


i get nothing in $post_info ( 'user' and 'post' are both tables in 'bluefirecode')

Yes, that seems very strange.

Make sure (through an echo or something) that the $post_id actually has a value set, and that an id with that value actually exists in the table.
Since the second query is not failing (at the mysql_query() call), that leads me to believe that the query executed, but there were no results (which is not an error) -- and with no results, then the 2nd 'fetch_row' call will fail because of an invalid $result2 value.

Maybe add this [before the line assigning $post_info] for the 2nd query attempt to see what might be happening:

Not letting you is alot different than returning nothing ... It's key to find out which is occurring.


You don't have the or die in your code snippet, but I'm guessing you have tried it their before. If you aren't getting into the OR DIE block, then it would appear that you ARE passing the DB a properly formatted query.


This is your brain ... This is your brain on having a bunch of databases with only one table each . You certainly don't want to do that. What you need to do is echo some key information (as TurboPT suggested). Probably the biggie would be echoing the query. Make sure that the query is populated with the values you think should be there. If it looks like what you think it should be, simply run the query on the mysql command prompt and see what it returns. It's obviously possible that the query just doesn't return anything.

After following all of what you said i finally fixed the problem. As it turned out i was trying to use a different database than the one that had all the info in it. (i'm in the process of merging all the separate db's into one) So on that part thanks for walking me through my stupidity . I really cant explain why it happened in the past though, it's in the past anyhow.

Peanut Butter Jelly Time!!! Keep in mind that a database should only contain tables that go together. Don't just put every table you have in one database for the sole purpose of having only one database.