05-19-2009, 12:53 AM
|
#25 (permalink)
|
|
Wizard
Join Date: Sep 2007
Posts: 1,299
Thanks: 17
|
Quote:
Originally Posted by TheOnly92
I think I'm going back to using my own custom method... I'm not too good at SQL programming and somehow SQLite hasn't got some admin panel or something...
|
SQL is fairly easy to learn, the initial concepts take very little time. Making your own custom format will be harder, less efficient and far less reliable.
Quote:
Originally Posted by TheOnly92
So is there any concept which will overcome my problem? When later sessions overwrite all the existing values?
|
Your options are pretty much SQL, an existing text storage method (CSV, XML, ect) and a custom method made by you. SQL is the easiest.
Quote:
Originally Posted by Enfernikus
Sessions persist until the user leaves the page ( I believe ) or until you destroy them
|
Partially true. Sessions exist until the machine destroys them. This can be manually or automatically done (the same exact process is called). If Apache works like IIS (it should in this respect), there is a set time limit till the server deletes the session, the session will remain until that period of inactivity has passed unless a manual deletion is called. This is because the server can not really know if you have left the page, all it knows is when you access it.
Sessions are not designed to be shared or constantly modified. Every time the session gets modified the computer has to modify the text file it is being held in (the format is almost plain text). If you have a value that is being modified very often over a large period of time, don't use sessions.
|
|
|
|