looping effect

[JakesSA]

Hi Guys

I have got a object with a constructor that pulls out a row from the database. When I want to do a multiple delete from the database, I have to loop the whole object, in order for it to call the constructor.

My question is.... is this best practice, or should it be done within the object itself?

thanks

[Natty_Dreadlock]

do not really understand your problem... Why "loop" the object after multiple delete when the constructor only fetches one row from your db... Be a little more precise. Code??

[JakesSA]

The constructor method gets one row from the database. I have other methods within the same class to either update, insert or to delete that row.

Now, if I want to update, delete or insert multiple rows into the database, I have to loop the constructor, ie. the class.

Does this not put strain onto the server, is this best practice?

[Natty_Dreadlock]

if I understand u correctly, u have to create multiple instances of your class to get the updated data??? So why don't u create a method that gets the data instead of using the constructor... I guess creating lots of objects just to call their constructor consumes more server time than simply calling a method of one object several times...
If i still did not get your point, please post a code example or something like this so I can see what the problem is and how u code it.