On 14 Mag, 13:15, subtenante <zzsubtenant...@gmail.com> wrote:
> to your description, i guess the input will be done "manually" (somebody has to fill a form somewhere,
> there is no complete automation). So the size of your database, I think, is not a big concern.

actually no, it will be completely automated (my mistake, i didn't
specify i meant it was a WEB game

but size is no issue anyway, as of now. this may be an issue later,
but i can't think of everything before having a finished product: size
and other optimizations may come later.

> EAV, as it is called (didn't know it me neither !), has the disadvantage to make searches more difficult.

ooh you're right.

On 15 Mag, 01:14, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> Search for "database normalization". It should give you some guidelines
> on what's the best for your case.

i will, thanks for the tip! (i searched "mysql optimization" before,
but found only crap things in the first two pages)

On 14 Mag, 13:46, subtenante <zzsubtenant...@gmail.com> wrote:
> Thinking twice myself, avoid the NULLs and put a default value instead
> (0 in general, I guess). NULL imply you are in a three-valued logic
> and the results of queries might not always be what they obviously
> should be.

hey nice idea. but. i kinda expected NULLs improved performance over
values such as 0, don't they?
well, having a slightly worst performance is anyway better than having
bugs you can't find, isn't it?
i'll consider this, thanks