Data Interface Objects
Posted: Fri Jun 22, 2007 10:01 am
fcarlier,
There are a few things that should be brought to your attention with your recent changes. First thing is, I noticed that you have been tending to replace all the Delete() functionality in the data interface classes with the simple DataObjectFactory<Type>.DeleteObject(Type object). However, deletions are not always this simple. For instance, in the patient class, one should not be allowed to delete patients (for cross referencing purposes), but instead the patient status should be marked to 4 (as provided in the function summary). Also, for mounts, when a mount is deleted, not only the mount object has to be deleted, but also the corresponding mount items. The same is true for in a mountdef and mountitemdef correlation. I also noticed that you have sometimes been using Path.Combine(), when we have created a custom combine path functionality ODFileUtils.CombinePaths(), which behaves slightly differently than Path.Combine(), and was created to help protect against quirks in the program when we began support for Unix. I hope this helps.
There are a few things that should be brought to your attention with your recent changes. First thing is, I noticed that you have been tending to replace all the Delete() functionality in the data interface classes with the simple DataObjectFactory<Type>.DeleteObject(Type object). However, deletions are not always this simple. For instance, in the patient class, one should not be allowed to delete patients (for cross referencing purposes), but instead the patient status should be marked to 4 (as provided in the function summary). Also, for mounts, when a mount is deleted, not only the mount object has to be deleted, but also the corresponding mount items. The same is true for in a mountdef and mountitemdef correlation. I also noticed that you have sometimes been using Path.Combine(), when we have created a custom combine path functionality ODFileUtils.CombinePaths(), which behaves slightly differently than Path.Combine(), and was created to help protect against quirks in the program when we began support for Unix. I hope this helps.