Re: Database schema

[sergey@total-knowledge.com]

Regarding "published field". I already suggested that it should be in DB
for every UMO b/c we will need to display each UMO's version creation date
on UI.

> I guess, the very least we can do is to add published field (DATETIME, I
> guess) to every UMO. If this field is NULL, then the object exists but can
> be seen by the UMO author only. In this case, any changes made in already
> published object are seen instantly (that is a disadvantage).
>
> 2007/1/18, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>>
>> I've checked the discussion threads including topic "Versioning", but I
>> can't seem to find it anywhere except " Translation vs. Versioning"
>> topic
>> in specs.
>>
>> http://www.total-knowledge.com/wiki/index.php/UU#Translation_vs._Versioning
>>
>> > There is another comment somewhere, which describes
>> > "published/unpublished"
>> > bit for a version, which suits better our current model.
>> >
>> > sergey@total-knowledge.com wrote:
>> >> I see. But I still need to know if we are going to save those copies
>> in
>> >> DB
>> >> or not. What if several users edit a same object at the same time?
>> >>
>> >>
>> >>> We have versioning support. If user creates a new version and then
>> >>> edits
>> >>> it
>> >>> many times - it is supported. Temporary copy of the object is not
>> >>> implemented.
>> >>>
>> >>> 2007/1/18, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>> >>>
>> >>>> Qustion regarding copy of UMO. Here is what we have in specs:
>> >>>>
>> >>>> ----
>> >>>> Object editing follows this pattern:
>> >>>>
>> >>>> 1. Edit Object action is requested. It creates a temporary copy of
>> an
>> >>>> object
>> >>>> 2. User edits and saves the copy (it can be saved as many times as
>> >>>> needed)
>> >>>> ----
>> >>>>
>> >>>> I can't find in which tables(fields) in DB schema those copys will
>> be
>> >>>> saved. Do we have it there and I'm just missing it?
>> >>>>
>> >>>>
>> >>>>
>> >>> --
>> >>> Alexey Parshin,
>> >>> http://www.sptk.net
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >
>> > --
>> > Ilya A. Volynets-Evenbakh
>> > Total Knowledge. CTO
>> > http://www.total-knowledge.com
>> >
>> >
>>
>>
>>
>
>
> --
> Alexey Parshin,
> http://www.sptk.net
>