Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
Date: Thu, 01 Jun 2006 19:53:42 GMT
> Marshall wrote:
>> There's a severe problem with that logic, though. >> >> If you want to build a layer to wrap a variety of different storage >> mechanisms, that layer *cannot* be any more powerful than >> the weakest mechanism you want to layer on top of. Which >> means your very high level, very powerful SQL dbms will >> be stuck at the level of the stupidest file store ever invented.
> I beg to disagree with that.
> If the wrapper/mapper is written to abstract the needs of the client,
> its representation can fully leverage the power of the specific storage
> regardles of any other implementation.
> Of course, such wrapper offers very specific services to its client,
> thus hiding the full richness of the strongest storage mechanism of the
> bunch. However this is OK, as the client (the domain) has very specific
> needs and that is precisely the purpose of the wrapper - to abstract
> those needs which then incidentally allows implementational variations.
With all due respect, Sasa, decomposing an application into cohesive components is not at all the same as separating database access to enable swapping out a dbms on a whim nor is it the same as establishing a layer to separate database access from everything else. Received on Thu Jun 01 2006 - 21:53:42 CEST