Home Projects Jobs Clientele Contact


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Latest DB schema

> What for?

As much a I know, we are going to use cookie-based sessions. What if
user's browser does not accept cookies?
Also imagine the situation when 2 authors change the same UMO at the same
time. In order to handle this we need to store each user session data in
session_table with something like:
1. sessionId
2. userId
3. objectId
4. lastVisitDate

So if changes were made to the UMO by second user with different sessionid
since lastVisitDate, we have to give first user a warning on submit or,
perhaps, make his changes versioned even if he chose minor.
Or, for better performance, we may add lastUpdatedDate column to each
*_content table and compare it with lastVisitDate from session_table on
each  update event.
In later versions session_table data may be used for user's bookmarks(UMO
basket) functionality, tracking order history data, etc.

> sergey@total-knowledge.com wrote:
>> IMHO, we are going to need a table in DB to store session IDs
> --
> Ilya A. Volynets-Evenbakh
> Total Knowledge. CTO
> http://www.total-knowledge.com

Authoright © Total Knowledge: 2001-2008