Re: Multi part attributes design question

Rik,

I fear there is no beautifull solution except to drop the sequence
number and try to do the ordering by other means, e. g. part code or
part name. The main problem is that SQL does set oriented processing
and as such is not good to handle one row at a time. All the table
inserts, updates and deletes would have to go via a special stored
procedure in order to avoid that the sequence numbers do not get out
of sync (Some good examples here:
http://unixadmintalk.com/f27/sequential-number-update-267509/).
If you update the table directly you easily destroy the sequence
number and then suppose you have a query that relies on the fact you
always have a sequence number 1 and at some places it is not available
- then your results are destroyed and there is much fun in repairing
this.

brgds

Philipp Post