[RESOLVED] General design advice...

[Studio381]

hi,
I'm finishing an application where there are a number of website members with connections to other members.

So when a member decides to terminate his membership I need to clean up any references that other members have to the member who is being removed.
This may take some time when the database gets large (2000+ members).
So what would be the best/safest way to design the clean up?

Give a "deletion ok" message asap and then goto another script to do the clean up or are there some other things I need to consider?

And if so how can I give a "deleted ok" message and then run another script?

Thanks,
john.

[Piranha]

2000 members with connections is still a small database. Just clean it up, nothing special needed.

[WDPEjoe]

If you're that concerned about it, what you could do is have the termination script delete the member's information, and then add the member id (however you identify them in references) to a file that will denote the "recently deleted" ids.

You can then run a PHP script via cron every x minutes that checks that file, cleans up references to the deleted members, then truncates that file. That way your reference termination system doesn't directly affect the processing of the user's termination web request.

[Studio381]

Thanks - I'll do that.
John.