|
|
Posted by ManChild on 09/21/05 03:11
> Exactly! I want to keep down the number of tables I have. I also want to now
> keep my tables & rows to a minimum. I want to keep my Db to a minimum. I
> also know that PHP takes a lot of effort.
>
> I like the idea of smoothing MySQL, I believe less columns, more data, less
> calls.
>
> It's a toughy. But it has to be less effort on the server, the better.
>
> I reckon bad PHP is as bad as bad MySQL.
>
As an experienced DBA I can tell you that forgoing indexing (leading
wild cards will force this) will have a significantly bigger performance
hit in the long run than coding multiple short queries.
Even if you do not do the query with a join, querying on explicit
numeric, indexed values will result in a miniscule query time for the
applicable cards -- you can't thumb your noise at normalization and
expect to get good results unless this is going to be a small database.
Why does it have to be a choice between bad PHP and by database
structure? Dont start off knowingly making bad choices :D Trust me -
it never pays!
J
Navigation:
[Reply to this message]
|