General information
Forum:
Microsoft SQL Server
OK, let's get back to your original question :) It's not a problem to delete a bunch of records in SQL Server, unless that this action violate an integrity rule in the database (you try to delete the parent record for example.) Like I said before, make sure to wrap your delete/insert operations inside a transaction and you're all set.
>Well in my VFP pos system I have an Inventory table that holds the model#, description, mfg, category ,etc. There is a child table that holds a record for each color/size/location matrix option which holds pricing information, quantities, and different sku numbers for each item.
>
>The shopping cart structure is different. While it has a main table for description, model, etc. The child table for holding variants has a variety of ways it can show the variants. If they only want one record to list on the web with a drop down for color/size combinations they would only have one child record where 2 fields exist one for a list of color options, the other for a list of size options,delimited with comma's. In the pos system they might add a color, delete a color, change the name of a color, etc.
>
>My thinking is it would be easier to delete the records in the shopping cart and then recreate the variant based on the children that now exist in the pos system.
>
>I hope this clarifies, However, I'm sure it doesn't :-)
>
>Which brings me to my original question. I don't think it would be *impossible* to "update" but there are quite a number of issues that will come into play. That is why I was asking if it's not a huge problem delete a bunch of records in SQL server this would difinitely be an easier option for me.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only