[Jope]

Is it better to store all data to one row or to store id's and query select later?

example

$name = "john";
$surname = "doe";
$status = "2"; // 2 is id for employee
now i need to get payment of employees
so i query
select `status` where 'id' = "2"
and get that payment

is it better to make this
$name = "john";
$surname = "doe";
$status = "employee-4000$";
and then
explode("-", $status) ?

i could remember only this example
in fact there are alot more datas like this and they are stored in more
than 3 tables.. so i think its stupid to query all time

there would be about 300 rows like this..

tnx

[NeverMind]

I prefere the first method, give you plenty of room for change..
you can use joins to merge the 2 SELECTs in one query..

[Jope]

Originally Posted by NeverMind

I prefere the first method, give you plenty of room for change..
you can use joins to merge the 2 SELECTs in one query..

So it is better to query 3 tables than about 100-200 characters more per row?

[NeverMind]

I thought they were only a couple of tables..
even tho, IMHO Joins are the way to go..