If you have the ability to do that then that's great, it's probably the
better choice in the long run.

On Sat, Mar 21, 2009 at 6:52 PM, David Perfors <[email protected]> wrote:

>
> Thanks Fabio,
>
> I have tried to get Burrow working, but that wasn't a success
> (although, I must admit I didn't have much time). But we found another
> way to deal with it. (Basically dumping the old database and start all
> over again.)
>
> Greetings,
>
> David.
>
> On Mar 19, 1:48 pm, Fabio Maulo <[email protected]> wrote:
> > There are various why to do it.You can know which SessionFactory know a
> > specific class. Burrow are using this method to ensure the session for a
> > specific class.
> >
> > 2009/3/19 David Perfors <[email protected]>
> >
> >
> >
> >
> >
> > > Hi,
> >
> > > In our project we have a situation where we can use a new database
> > > (tables generated by NHibernate), but we also need data from existing
> > > databases (a compete different kind of database engine...).
> > > In our domain there is a relation between objects that are stored in
> > > the new database and objects that are stored in the second database.
> >
> > > Since I am quite new to NHibernate I was wondering what possibilities
> > > there are to accomplish this. I know that I need two separate
> > > SessionFactories, (for each database/dialect one) but how can I tell
> > > NHibernate that it should use a different session for specific
> > > classes?
> >
> > > I am currently looking into the IInterceptor interface to find out
> > > whether that is suitable for this, but I am not convinced it is. Any
> > > suggestions, clarification, etc?
> >
> > > David
> >
> > --
> > Fabio Maulo
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to