Forum Moderators: open

Message Too Old, No Replies

compact

         

stevelibby

10:15 am on Oct 22, 2007 (gmt 0)

10+ Year Member



hi guys i have a table with about 60000 rows in it which gets updated frequently, adding,deleting and so on, is it better too...
instead of each row being deleted that, lets say i empty row and then any update will look for an empty rows before adding a new one?

Demaestro

8:53 pm on Oct 22, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I think it is better to just stick to the delete and update/inserts.

It could get ugly with a bunch of empty rows and your code to find them and update them and all that could get ugly and hard for someone else to come into and make changes. Heck in a year if you don't touch the code again it could make it hard for you to come in and make changes.

If you are worried about size and memory not being properly re-allocated after doing a delete you can always perform some kind of "packing" function on it.

Almost all DBs have sometime of function for packing the data.