John,
I would love to do that, but I don't know what code would be helpful here.
All of it is quite trivial really. As far as the exception it is also quite
uninformative, here it is:
System.NullReferenceException was caught
Message="Object reference not set to an instance of an object."
Sou
For future reference I would like to know how I could have handled this
situation using NHibernate, so if you'll bear with me I'll give you a brief
synopsis of what I am trying to achieve. This is a transportation/logistics
application.
User creates or opens a job
A job for these purposes contain
Josh,
Some code and a copy of the exception message would allow everyone to
help you better.
Cheers,
John
On Jul 2, 5:34 am, jobsamuel wrote:
> I thought that since you are using db generated identity, your save
> would result in a db call and your further call to criteria query
> would work.
I thought that since you are using db generated identity, your save
would result in a db call and your further call to criteria query
would work. Even if you are not using db generated id the session
would automatically flush upon a query and your criteria query should
still work. I think this is
2009/7/1 Graham Bunce
>
> >You can even explain the "logic" to NH using ;)
>
> Sheesh, I've just about got my head around NH 2.0.1GA without getting
> my head around all the new 2.1.0 features!!
Stay updated... stay updated the world of Open Source is going fast. ;)
--
Fabio Maulo
--~--~
>You can even explain the "logic" to NH using ;)
Sheesh, I've just about got my head around NH 2.0.1GA without getting
my head around all the new 2.1.0 features!!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"n
2009/7/1 Graham Bunce
>
> And to explain your issue, NH always goes to the DB for a query. I
> suspect this is for performance reasons as how can it search its cache
> on any number of unknown (by the NH designer) parameters that a
> developer will provide? It would just be too slow. Therefore it
Understandable but many of the issues you get with NH (using
Identities generated by a DB for example) you can run into with other
ORM's or ORM-like products such as Linq-SQL. Fabio (quite
understandably) has a thing against DB identity and will usually be
quite aggressive against it and not alway
Ok, well I have spent the last 4 weeks trying to bend my application to work
with NHibernate and I can't lose anymore productivity so I am going to have
to pull out NHibernate and go back to dealing with ADO directly or find
another ORM solution.
I just wanted to thank everyone for their time, it
2009/7/1 Josh Rogers
>
> As far as the POID strategy I am using the db generated ID that increments
> by 1 each time a new item is added.
If you mean identity you must know how identity work.
Identity break the UnitOfWork pattern and session.Save mean a INSERT to DB.
If you want work with conve
Ok, but how do I get it to look at the cache first? I don't want it to
query the db until it can't find the object in cache, that would seem the
natural order of things.
As far as the POID strategy I am using the db generated ID that increments
by 1 each time a new item is added.
JOsh
On Wed,
Query mean always "query-to-db", after the query to DB is executed the
session-cache begin working returning you the existing instance in the
session-cache or attaching new instance.Btw because you are talking about
"conversation" we must know the POID strategy you are using.
2009/7/1 Josh Rogers
12 matches
Mail list logo
