Not following. What do you mean doesn't matter? The transaction setting? Because NHibernate doesn't have different behavior based on that.
On Wed, Sep 24, 2008 at 3:36 PM, ndotan <[EMAIL PROTECTED]> wrote: > > thanks for the very quick answer ayende > can you elaborate why the model doesnt matter? > > > On Sep 24, 3:33 pm, "Ayende Rahien" <[EMAIL PROTECTED]> wrote: > > On Wed, Sep 24, 2008 at 3:27 PM, ndotan <[EMAIL PROTECTED]> wrote: > > > > > hey guys i was presenting NH, and got some questions.. > > > > > 1. what happens if DB not support transactions and im trying a > > > transaction > > > > An exception is thrown. NHibernate mandates the use of transactions. > > > > > 2. is the transaction model pesimistic? > > > > Doesn't matter. > > > > > > > > > 3. when i use session.Get twice in a row, NH doesnt query the DB again > > > and gives me the same instance, > > > when does NH know to go to the DB and update that entity? how does > > > it know that the database row was changed in order to go to the DB? > > > > It get it from the session first level cache. It doesn't go to the DB and > > you'll get stale object exception if you setup concurrency right and > someone > > changed the row underneath you > > > > > sidenote(slightly offtopic, but it came up in the presentation): > > > is MS entityframework with oracle a fiction? > > > > I haven't seen or heard anything about it. It may exists, though. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
