Comments on: symfony Doctrine database session storage

By: Merci Symfony « Tout sur Rien

Merci Symfony « Tout sur Rien — Mon, 12 Apr 2010 00:35:06 +0000

[...] Alistair Stead pour son article « symfony Doctrine database session storage« [...]

By: Alistair Stead

Alistair Stead — Tue, 06 Apr 2010 20:21:55 +0000

Depending upon you ini config the sessions should be removed automatically.

By: Saad

Saad — Tue, 30 Mar 2010 19:10:57 +0000

Hi,
Great post! I just used it because the prod servers we had to use were load-balanced and we were not able to install memcache.
The only concern I have: how to clear timed-out sessions? We created a (really simple) symfony task for that, because we weren’t sure if there is some “symfony magic” that automatically clears sessions. I haven’t find any. If you don’t clear expired sessions, I think the DB table will grow infinitely, right?

By: tmv

tmv — Tue, 23 Mar 2010 13:10:01 +0000

to define id column can be use param fixed:true then id field will be fixed size char(32) not varchar(32) and performance should be better.

id: { type: string(32), primary: true, notnull: true, fixed:true }

Thanks for this great tutorial!

By: victor

victor — Sat, 20 Feb 2010 21:13:08 +0000

Yes, I know that. But I refer to specific users, not at the number of logged in users.

By: Alistair Stead

Alistair Stead — Sat, 20 Feb 2010 07:00:25 +0000

Hi,

You can simple make a select on the session tabe and count the results. If everything is setup correctly the data rows are deleted after a user leaves the site.

By: victor

victor — Wed, 17 Feb 2010 12:19:31 +0000

Hi,

You said that by storing sessions in a database you are able to retrieve logged in users. Could you please give an example of how to do this?

By: Alistair Stead

Alistair Stead — Sat, 13 Feb 2010 10:07:23 +0000

Hi,

Symfony uses the standard PHP session handler. Due to how a session must be stored and retrieved between each HTTP request the data is stored in a serialized form. Unless you are storing large object structures in session this should not cause you any problems. I’m unsure of your requirements to store data in columns?

I would suggest that you should possibly look at adding additional protected variables to the myUser class and then create getter and setter methods that will retrieve the data from session. You can then access the data through a common interface.

By: Balazs.2.0

Balazs.2.0 — Tue, 26 Jan 2010 00:50:23 +0000

Hello,

What I’m wondering about (and sorry of this is a newbie question) is that, symfony stores the session data in a serialized form. Can this be changed? More importantly, should this be changed? I usually see session data stored in columns seperately. Does this mean, that each time session data is requested, you have to de-serialize it? Does that effect performance?

Thanks

By: Tom

Tom — Wed, 20 Jan 2010 22:50:47 +0000

Excellent, thanks for this very straightforward explanation, plus comments from other commenters.