At 11:45 AM 3/21/2007 -0700, Morgen Sagen wrote:
[This is mainly a pje question, but I thought I would CC dev in case
anyone else had an opinion]
I realized this morning that we need to solve the following problem:
Any item that is created "out of the box" on a clean repository -- in
other words, every item that is created by an update( ) call within
an installParcel( ) -- should not be dumped. If they are, then we'll
get duplicates the next time a brand new Chandler is run and the data
is reloaded, since the items created via update( ) will have
different UUIDs the second time around. The "Welcome Note" is such
an item; if we dump it, run Chandler with a fresh repo, and reload
the dump, we'll have two such notes.
So I was thinking we could add an attribute to schema.Item called
"is_user_data" or something which has a default value of True.
schema.Item.update( ) would set this to False.
Wouldn't it suffice to just not dump anything under the parcels
tree? After all, update() can be used for non-parcel items, and you can
create parcel children without update().
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
