Currently i have a system setup for users to pick songs for there wedding reception. This works fairly similar to a shopping cart. I did not write the site using sessions rather i wrote it using cookies.. I plan on upgrading it with sessions, and allowing users to use the site without having registered.. of course they will need to register before they can complete. Currently they can browse songs but can't add them tot here "cart". What i need to know is a good way to integrate the two, between a user who has not yet registered's songs with the user once he registers..
Currently the user registers his/her name and that is his unique identifier (other than the built in unique id). I'm thinking i would have to take the session ID and use that as the users i'd.. then once he registers i need to like rename that to the name he registers right? I'm not really sure if thats the way it typically gets done..
I would almost prefer to put a temp into another table that way i don't store a bunch of extra information that will never get used (for all the users who do not follow through with registering and using this service).. What do you guys think about this? Also, if i do that, what is the best way to "recycle" the system (i dont know if thats the right term i just made it up). I'd like to store say up to 25-50 temp accounts before the first gets replaced with a new one.. I suppose i would have to run a query to find the lowest id (not sure how to do that) and remove that entry.