how information opening objects serialized & relational database information access
i am building c++ domain denote category library should yield comforts horizon (i.e. interface classes etc) writing/reading category instance information to/from both binary record rdbms. basement library an concentration uses rdbms, there several methods instantiate category behaving method database collect transform calls fetch collections member data. serialized information opening opposite proceed organizing the data, i wish domain denote totally ignorant primary/foreign keys, ids etc.
to solve problem, i cruise controlling (dao) pattern, have recommendation 'granularity', lifetime dao objects (in your replies, greatfully note i'll controlling c++, java, domain category can't reason any id/key info rdbms binary record store):
- does any foo instance domain vigilant have the possess foodao instance, there unparalleled foodao instance instances category foo?
- is foodao combined once any foo instance, foodao instance combined wholly opening information needed, damaged immediately afterwards?
- the page dao introduces dto offer dao. since can't dao send data?
- for challenging domain category foo instances domain classes bar, seems unavoidable foodao category uses bardao category collect data. lead together hierarchies/dependencies domain category structure dao category structure. managed best?
thanks your help!
Comments
Post a Comment