On Wed, 2002-07-31 at 02:34, Andrew Sullivan wrote:
> Why not three codes: model, colour, and size? Then you can query all
> by model, and limit by size, colour, or both.
How do you mean three codes?
If you mean having more than one product code for a type of shoe thats
what I am trying to avoid. I worked for acompany that did that a long
time ago, the product was steel, and having 15 or more different lengths
of a steel chanl meant having 15 product codes. It was often easier to
walk out to the store and look for the product than to query each
product code at the counter...
> I think your strategy will work, but it has the potential to degrade
> seriously over time, or else to require some sort of regular
> maintenance. Nothing wrong with that, of course, just a potential
> pitfall.
One thing I am thinking is having a duplicate table called
history_transactions, and at a stock take move all the transaction rows
into the history table. That way we have the total history, but ding a
search for products in stock is useing a smaler table.
Taht said, maybe do the history thing at the end of each financial year
rather then each month or quater depending on how many transactions they
are getting (at the moment it's less than 50 per store per day, so less
400 a day on a good day, but other potential customes could well be
busier)
--
*
* Rob Brown-Bayliss
*
