mysql query problem

fuzic

I have a query which works;

$resultf = mysql_query('SELECT `user_id`,`post_time`,`post` FROM `1` WHERE `thread_id` = "'.$t.'" LIMIT 0, 30');

but then if I replace 1 with a variable, like so

$resultf = mysql_query('SELECT `user_id`,`post_time`,`post` FROM "'.$f.'" WHERE `thread_id` = "'.$t.'" LIMIT 0, 30');

where $f=1, it doesn't work.
Thanks in advance.

note; in the first query listed, it only works with the ``s in it.

LordShryku

It works in the first query because you're using backticks around 1, and in the second one, you've replaced the backticks with double quotes.

Just out of curiosity....what on earth would possess you to name a table "1"? That screams horrible database design

fuzic

thanks
and about the table name, I was going to have 6 sections to a forum, so I named each of the tables numerically, and each number is associated with a name stored in an array... not a good idea?

Moonglobe

Originally posted by fuzic
thanks
and about the table name, I was going to have 6 sections to a forum, so I named each of the tables numerically, and each number is associated with a name stored in an array... not a good idea?

no. you will invariably forget what numebrs represent what sections.... and more importantly, anyone else who looks at your code will have NO idea what's going on!

LordShryku

A good rule of thumb for you with MySQL: If it only works when you put backticks around it, it's not good. Means it's either confusing MySQL, or it's reserved, or it's just invalid. As far as database design is concerned, it's definately not a good table name. It's the equivalent of naming the fields "field1", "field2", "field3", and so forth. You'll eventually forget what goes where, when you could have just gave them proper names, and wouldn't be stuck.

Then again, I'm just anal about this stuff.

fuzic

good point... thanks for the advice

ultraslacker

Originally posted by fuzic
thanks
and about the table name, I was going to have 6 sections to a forum, so I named each of the tables numerically, and each number is associated with a name stored in an array... not a good idea?

What is your database design? One table per section is not what I would recommend. It is clunky - if you add another section, you have to add another table, and searching posts means six times the work for the dbms (and dba). Use one table for sections.

There are plenty of open source forums out there, anyway, so take a look at one of their database structure.