For developers who are modifying the values of Documents properties (for example in a batch update or import) it would be a welcome feature to get rid of the "immediately save new property value to database" functionality. Since this is a performance decreasing devil.
A better way that I have seen in other Content Management Systems is to set the item in an "edit-mode" to make it possible to modify property values -> modify the property values -> end "edit mode" which automatically saves all the changes of this item back to the database.
There's actually a good reason why the saving happens when it does. The design of the DataType allows anyone to be able to implement them to do almost anything.
The standard way to use a DataType is to write to the Umbraco database, but you don't have to do it that way, you can write to an XML file, call a web service or actually have no data saving.
Because of this it's up the responsibility of the DataType creator to do the CRUD operations, it's not possible to have Umbraco have some kind of a global save operation (because what if there wasn't a save!).
Whether or not DataTypes stay this flexible in Umbraco 5 is yet to be seen though.
Feature request to improve performance when modifying Document through API
For developers who are modifying the values of Documents properties (for example in a batch update or import) it would be a welcome feature to get rid of the "immediately save new property value to database" functionality. Since this is a performance decreasing devil.
A better way that I have seen in other Content Management Systems is to set the item in an "edit-mode" to make it possible to modify property values -> modify the property values -> end "edit mode" which automatically saves all the changes of this item back to the database.
I agree on this one. It's too late to change this in Umbraco 4, but I recommend the above approach for Umbraco 5. Could save a lot of performance!
P.S. It might be a good idea to make a workitem for this: http://umbraco.codeplex.com/workitem/list/basic
I just created a work item for this. Thanks for the tip.
I already vote for you workitem :). http://umbraco.codeplex.com/WorkItem/View.aspx?WorkItemId=26687
There's actually a good reason why the saving happens when it does. The design of the DataType allows anyone to be able to implement them to do almost anything.
The standard way to use a DataType is to write to the Umbraco database, but you don't have to do it that way, you can write to an XML file, call a web service or actually have no data saving.
Because of this it's up the responsibility of the DataType creator to do the CRUD operations, it's not possible to have Umbraco have some kind of a global save operation (because what if there wasn't a save!).
Whether or not DataTypes stay this flexible in Umbraco 5 is yet to be seen though.
is working on a reply...