CST with Ext.session data container (SQL)
Hi All, I would like to try CoreSessionTracking 0.9 with External data container, to store session data in a SQL table. I figured that I'll need to instantiate Session Data Container. But there is no place in Session Data Container management screens to specify the SQL connection to use. OTOH, Session Data Manager has a place to specify Session Data Container. So I now have Session Data Manager pointing to correct Session Data Container, but I don't know how to point Session Data Container to a SQL table. -- Milos Prudek
CST does not support relational databases for session data storage. Al data is stored in the ZODB (mounted or main). Milos Prudek wrote:
Hi All,
I would like to try CoreSessionTracking 0.9 with External data container, to store session data in a SQL table.
I figured that I'll need to instantiate Session Data Container. But there is no place in Session Data Container management screens to specify the SQL connection to use.
OTOH, Session Data Manager has a place to specify Session Data Container.
So I now have Session Data Manager pointing to correct Session Data Container, but I don't know how to point Session Data Container to a SQL table.
-- Milos Prudek
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
I would like to try CoreSessionTracking 0.9 with External data container, to store session data in a SQL table.
CST does not support relational databases for session data storage. Al data is stored in the ZODB (mounted or main).
Sorry for the confusion! I misunderstood the following texts from CST help: ++ External session data containers are traversable, and they are meant to be instantiated within a nonundoing database, as accesses to session data containers are very write-intensive. (...) A heavily-utilized external session data container should be instantiated inside a database which is nonundoing! ++ Obviously, I do not understand the term "to mount a nonundoing storage". Does that mean "to mount a storage system, such as SQL table, inside ZODB, so that it behaves transparently as part of ZODB tree"? Can you give some URLs where I would learn about that -- Milos Prudek
Obviously, I do not understand the term "to mount a nonundoing storage". Does that mean "to mount a storage system, such as SQL table, inside ZODB, so that it behaves transparently as part of ZODB tree"?
No. A "storage" is a ZODB concept which means a literal Python object that implements the Storage interface. "Nonundoing" means that the storage doesn't support undo operataions (ala the Zope Undo tab). The doc means "mount another ZODB storage that is nonundoing".
Can you give some URLs where I would learn about that
Sure. http://www.zope.org/Members/mcdonc/HowTos/UseExternalMountWithCST -- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
participants (2)
-
Chris McDonough -
Milos Prudek