1

So, according to Ayende Lazy Loading Properties are already in the NHibernate trunk.

My Problem is: I can't use the trunk for I have FluentNHibernate and LinQ for NHibernate, so I depend on the version they are linked against (Versio 2.x). I can't and don't want to build all the assemblies myself against the newest version of NHibernate.

So, has someone got information about when NHibernate 3.0 will leave Beta-Stadium and the auxiliaries (Linq etc.) will be compiled against it?

I appreciate any estimate!

I need this feature so I can use it on Blob-Fields. I don't want to use workarounds to destroy my object model.

2 Answers 2

3

You can compile Fluent with the NH 3.0 binaries, and you don't need L2NH anymore; there's a new integrated provider.

Sign up to request clarification or add additional context in comments.

1 Comment

Please see this post here: stackoverflow.com/questions/4163374/…
0

Alternatively it isn't much of a model change. Make a new class, Blob, that has Id, Version and Bytes properties, make a new table to match. Add the new class as a protected property to each of your classes that currently has a blob. Use it like a backing store. Change your mapping to map the underlying property instead of the public one.

public class MyClass
{
    public MyClass()
    {
        MyBlobProperty_Blob= new Blob();
    }

    public virtual byte[] MyBlobProperty
    {
        get { return MyBlobProperty_Blob.Bytes; }
    }

    protected virtual Blob MyBlobProperty_Blob { get; private set; }
}

It is a significant schema change however. This particular solution moves all your binary data into one table.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.