[UPHPU] Inventory Databases

[cole at colejoplin.com]

Justin,

If records are not going to be queried often, maybe consider adding a  
status_id field (int signed) to your table. You could use this field  
to make records obsolete, special, or tagged with an error code. As an  
example, just modify your sql statement like:

"SELECT YourTable WHERE (YourNormalCondition=true) AND (status_id=1)"

Don't forget the index on status_id. You could always export the  
records off into some archive table later, but for now, it's a nice,  
fast solution.

-- Cole




Quoting Webot Graphics <graphics at westernbotanicals.com>:

> When creating an Inventory Database, is it best to keep all the records
> coming in, in one table? The main thing I am worried about is that
> after a year or two, there could be quite a few entries that would not
> really be necessary for the query to search through. Does anyone know
> about any good inventory database tutorials.
>
>
> Justin Giboney
> graphics at westernbotanicals.com
>
>
>
>
> _______________________________________________
>
> UPHPU mailing list
> UPHPU at uphpu.org
> http://uphpu.org/mailman/listinfo/uphpu
> IRC: #uphpu on irc.freenode.net