On Friday 14 May 2010, you wrote:
> yes, but I am not sure, which version is more desirable
> (1) reset the complete record on reload
> (2) maintain user (admin) changes
>
> but it's strange that after reloading an xml file the db-content is
> different from the file.
>
> it's even worse if an act_window is deleted in the xml , it never gets
> deleted in the db.
>
> IMHO this needs a more detailed investigation.
>
This would call for several new features in the ORM :
- <record id="the_old_id" action="delete" /> element (say..)
- Field-level xml loading and complex rules.
- Much more attention in writting those xml's. It is not enough if they only
work for a new database.
On Friday 14 May 2010, you wrote:
> yes, but I am not sure, which version is more desirable
> (1) reset the complete record on reload
> (2) maintain user (admin) changes
>
> but it's strange that after reloading an xml file the db-content is
> different from the file.
>
> it's even worse if an act_window is deleted in the xml , it never gets
> deleted in the db.
>
> IMHO this needs a more detailed investigation.
>
This would call for several new features in the ORM :
- <record id="the_old_id" action="delete" /> element (say..)
- Field-level xml loading and complex rules.
- Much more attention in writting those xml's. It is not enough if they only
work for a new database.