There is another way to go, when talking about Persistence Ignorance.
I define all my model entities as interfaces in a separate assembly.
I have a code generator specific for each storage that takes care
of all the plumbing for me:
1) generates the classes as the storage wants them : NH
Liviu, We would be glad to accept all the help that you can provide with
writing documentation.
On Wed, Oct 8, 2008 at 8:57 AM, Liviu U [EMAIL PROTECTED] wrote:
Regarding : code it yourself advice, this is the biggest pain in the
with open source projects that do not have the guts to
PI has always been defined as the domain not having any changes in
specific for it persistence mechanism.
I believe we can give credit to Jimmy Nilsson for creating in the term
in ADDDP (Applying Domain Driven Design and Patterns).
You could use nhibernate in a more classic repository
Greg,
IInterceptor.Instansiate ?
On Tue, Oct 7, 2008 at 10:06 PM, Greg Young [EMAIL PROTECTED] wrote:
PI has always been defined as the domain not having any changes in
specific for it persistence mechanism.
I believe we can give credit to Jimmy Nilsson for creating in the term
in ADDDP
Let me clarify, it supports it. It's just very painful in implementation...
On 10/7/08, Ayende Rahien [EMAIL PROTECTED] wrote:
Greg,
IInterceptor.Instansiate ?
On Tue, Oct 7, 2008 at 10:06 PM, Greg Young [EMAIL PROTECTED] wrote:
PI has always been defined as the domain not having any
Write your own is never a very good answer. I know I was bringing
up a touchy subject, but was hoping to avoid defensive answers. I
like the performance the proxies give me, and I like the support for
lazy loading, but that doesn't mean there aren't restrictions and
shortcomings.
I actually
You can selectively intercept by using EmptyInterceptor as a base class,
which will also deal with the default behavior appropriately.
That was not a defensive answer, by the way, that was an expression of
intent. If you don't like it, fix it.
The source is there, and the architecture supports
The EmptyInterceptor is exactly what I needed. This is excellent, now
I can get all that auditing in there that I want. Thanks!
On Oct 7, 1:27 pm, Ayende Rahien [EMAIL PROTECTED] wrote:
You can selectively intercept by using EmptyInterceptor as a base class,
which will also deal with the
MAMMON [EMAIL PROTECTED] writes:
So does NH really achieve Persistence Ignorance?
IMNSHO it's a dumb idea to try to make your business layer completly
persistence ingnorant (in the way you suggest), because there is some
persistence in the background and you are developing a complex
system.
Funny in past conversations you determined that supporting constructor
mapping would require so much rewriting/rearchitecture that it wasn't
viable to look at ...
Now you ask me for a patch.
hmm.
Cheers,
Greg
On Tue, Oct 7, 2008 at 1:18 PM, Ayende Rahien [EMAIL PROTECTED] wrote:
Patch it to
I did? I don't recall that.
Ctor mapping isn't really different than the other forms of mapping that
Nhibernate has.
It is different because you need to gather the data up front and then create
the instance, but it is possible.
Start from Loader.GetRow and move from there.
It is not trivial, but
2008/10/7 MAMMON [EMAIL PROTECTED]
but it DOES:
+ Force me to make all of my methods and properties virtual, for the
use of proxies
It is not NH. It is a requirement of Castle.DynamicProxy and in general a
requirement of any kind of DynProxy.
Unluckily .NET don't give us a buildin system
2008/10/7 MAMMON [EMAIL PROTECTED]
With a lot of Entity Framework buzz being generated recently, due to
it's v1 release with VS2008 SP1, the term Persistence Ignorance has
been climbing the Google ranks ladder. Indeed, a Google search of the
term shows that of the top 5 results, 3 are about
If EF is the future, then I don't want to see tomorrow.
On Tue, Oct 7, 2008 at 5:50 PM, Fabio Maulo [EMAIL PROTECTED] wrote:
2008/10/7 MAMMON [EMAIL PROTECTED]
With a lot of Entity Framework buzz being generated recently, due to
it's v1 release with VS2008 SP1, the term Persistence Ignorance
inline, having played with the POCO adapter for EF, my 2 cents would be do
not use it, and not let any of your good friends do so. Seriously, PI is not
that important to create 3 levels of mapping just to achieve it. (even the
built in 2 makes me choke, but that's even another inline discussion)
15 matches
Mail list logo
