Home Projects Jobs Clientele Contact


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

Re: Latest DB schema

I see what you mean, but it's still don't understand how to check
constraints information in DB schema.
For example, combination "pl_login + pl_password" in person_list should be
unique for each user. How is it reflected in the schema?

> I don't think there is a way to identify the duplicate UMOs. From the
> point
> of the database, if the user creates a new version - then it's a different
> UMO already.
> And if he doesn't (performing minor changes) then a copy of the UMO isn't
> created.
> If two users create two similar versions of the same object - they may
> want
> to create a different set of connections, like ACL, for instance, and make
> more modifications later. I don't think we can predict their logic in the
> later modifications.
> 2006/11/11, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>> Is there any way to see constraints in DB schema? Maybe it's there, I
>> just
>> don't know how to read it.I assume we don't want user to create bunch of
>> identical UMOs on each update if no changes were made to the UMO.
>> Also what if(theoriticly speaking) 2 users create exactly the same UMO
>> or
>> make exactly the same versioned change to UMO(like fixing an obvious
>> syntax error by the original author)?
> --
> Alexey Parshin,
> http://www.sptk.net

Authoright © Total Knowledge: 2001-2008