How can you implement without CRUD?
Raised up in the happy ADO.NET world, I am wondering how the CRUD operation is managed without changing with POCOs.
Manages data by removing, adding, or modifying a common pattern control and data user rows for typical fat customer solutions. Data is then written in the database using a save () command. Working with POCOs, I saw that most frameworks (like or) alter the conversion tracking and I'm wondering how strong the pattern to work may look like POCOs.
One of the complex business applications can send an update x to y command after another without using any transaction etc. And I do not have any changes in this bundle for example, after clicking on "Save", the user has a single command.
Unless I am mistaken, if you want to store all the changes and then "save them" "If you want to submit to the command, then you have to have some kind of change tracking. Whether it is applicable with an ADO transaction or you roll your own pattern.
You can of course control the operation of the CRUD without changing it as you mentioned but the CRUD should be operational immediately.
If I had, I would look at available tools (can you use the unit framework for example?) - look at the need to really track changes and implement a change tracking mechanism. Weighing the time the development time will take you may find that operating the CRUD is the best option.
Comments
Post a Comment