Tray to make a question at time... For each class the CRUD queries are created in AbstractEntityPersister and inheritors but only "may be" because NHallow custo-queries. Same for AbstractCollectionPersister and inheritors.
You have the "start point", good luck!! 2010/2/23 George Mauer <[email protected]> > Guys, don't get me wrong, I'm not looking to have someone do all the > work for me. It's just a little hard to know where to start. If you > can point me at a namespace, and let me know what concepts/design > patterns to look out for that should suffice (at least until I come > back here with a list of specific questions). > > > On Feb 23, 11:08 am, Shane Courtrille <[email protected]> > wrote: > > Have you considered reading the code? > > > > > > > > On Tue, Feb 23, 2010 at 9:46 AM, George Mauer <[email protected]> wrote: > > > Hello, > > > I am writing code that needs to treat the database in a database- > > > agnostic way. There is no domain model per-se so I cannot use > > > NHibernate directly but I would like to look at how NHibernate does > > > it's database agnosticism and then maybe re-use that part of it. > > > > > Is there an overview somewhere specifically of this part of the > > > architecture? If not, can someone help me out with understanding it? > > > > > Specifically the questions that I have at this moment are: > > > > > 1) Does NHibernate have an abstraction layer between the domain > > > objects and database-specific queries? Where is it and what does it > > > roughly look like? > > > 2) What exactly is the flow from an hql query to sql? > > > 3) What are the components that translate the abstraction to generate > > > the final sql? > > > 4) Is there a separate area where the tests for all this are located? > -- Fabio Maulo
