Moti Asayag has posted comments on this change. Change subject: engine: Introduce VmNicDao ......................................................................
Patch Set 6: (1 inline comment) .................................................... Commit Message Line 3: AuthorDate: 2013-07-21 23:21:24 +0300 Line 4: Commit: Alona Kaplan <alkap...@redhat.com> Line 5: CommitDate: 2013-07-25 18:52:02 +0300 Line 6: Line 7: engine: Introduce VmNicDao The reason for a separate DAOs relies on the difference on the entities being managed by the DAOs itself. Since a dao should be associate with a certain entity, and due to desire to isolate the backend internal managed entities from these being enquire by the clients. VnicDao - is the DAO for managing entities of vm_interface table. VmNetworkInterface - a read-only DAO used for enquire entities from vm_interface_view (based on several tables) Line 8: Line 9: The VmNicDao will serve as the DAO api for persisting Line 10: VmNetworkInterface entities to the data base. Line 11: It replaces the former VmNetworkInterfaceDao which will -- To view, visit http://gerrit.ovirt.org/17178 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ib3d1ff6dfc415915244367c153ffc064ddd0d0df Gerrit-PatchSet: 6 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Moti Asayag <masa...@redhat.com> Gerrit-Reviewer: Alona Kaplan <alkap...@redhat.com> Gerrit-Reviewer: Moti Asayag <masa...@redhat.com> Gerrit-Reviewer: Shubhendu Tripathi <shtri...@redhat.com> Gerrit-Reviewer: oVirt Jenkins CI Server _______________________________________________ Engine-patches mailing list Engine-patches@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-patches
