[thelist] worldusa.com sucks

> let's say you have this in your current shopping cart minischema
> [snip]
> You can eliminate the second table altogether by adding a field to CART
> called ITEMS_XML or whatever. Within ITEMS_XML would be stored:
>
><item>
>    <prodid></prodid>
>    <taxcatid></taxcatid>
>    <quant></quant>
>    ...
></item>
><item>
>    <prodid></prodid>
>    <taxcatid></taxcatid>
>    <quant></quant>
>    ...
></item>

beauty

do you actually store them in the database that way? i haven't used an xml
database yet

i thought that in order to generate xml output, you query them out of a
regular database and use the column names as the xml tags...

i think you'd still want to have an ID field (surrogate primary key) unless
you were using PROD_ID as the pk (also a possibility, but you wouldn't be
able to add product descriptions without assigning them a product id first)

matt, you didn't use the cart's CREATED_DT anywhere, so even in a regular
database, you can eliminate the parent table

;o)

_____________
rudy limeback
http://r937.com/
http://evolt.org/