Re: Latest DB schema

["Alexey Parshin" <alexeyp@gmail.com>]

IMO, any preferences that are not one-to-many (ie not a list), like preferred_language, may go into person_list.
As for the others - we would need to discuss it separately, since it probably requires support on the database level.
The notifications, for instance, belong to an object.

2006/10/31, sergey@total-knowledge.com < sergey@total-knowledge.com>:

> sergey@total-knowledge.com wrote:
>> I think we may need something like person_preferences table to handle
>> user
>> preferences for
>>
>> 1. Prefered UI language.
>>
> Good point. Although this might be just a field in person_list

IMO a new table may be better, since user may have many additional
preferncies(email notifications for ordering, currency, the way UI
displays certain UMOs/features, any kind of
restrictions/limitations/preferencies for UMO he is an author of, etc).


>> 2. Object change notifications/preferencies.
>>
> No, these are per-object-relation. Although you are right in that
> the info is missing.
>> Also we need to handle user types somehow, probably using user_types
>> table.
>>
> There are no user-types as such. There are access kinds users
> have to different objects. ACL tables handle that.
>
> --
> Ilya A. Volynets-Evenbakh
> Total Knowledge. CTO
> http://www.total-knowledge.com
>
>

-- 
Alexey Parshin,
http://www.sptk.net