Now I must sheepishly confess the source of my problem. I was barking up the entirely wrong tree.
NHibernate was working perfectly fine. The field in question was binary data in a byte array, so it was not easy to inspect. However, there was another part of the application that was visualizing that binary data, so we could tell it had not changed. Couple that with fine-grained debugging where NHibernate would refuse to UPDATE because it believed the binary data was not dirty, and you can begin to understand my frustration. It turns out, though, NHibernate did update the binary data during the first attempt last week. However, the portion of the application that renders it was using Memcached, so IT was still rendering the old visualization! Caches are a double-edged sword. On Oct 12, 10:39 am, Trinition <[email protected]> wrote: > I just created a new solution and project, copying over the bare > minimum pieces. In this cleanup, the problem is NOT occurring. The > test is consistently UPDATEing the rows. > > I don't feel like I cut out anything fundamental that would've side- > stepped my issue. While I was hoping to have some better diagnostics > I could do against the current code base, I at least know that my > intended design works just fine, but there's some subtle difference I > can't see. > > Regards, > Brian. > > On Oct 9, 5:21 pm, Tuna Toksoz <[email protected]> wrote: > > > > > Isolation of the problem into a test case would be awesome, but you can > > start by showing entity and its mapping and the code that exhibits the > > behavior. > > > Tuna Toksöz > > Eternal sunshine of the open source mind. > > >http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitt... > > > On Sat, Oct 10, 2009 at 12:18 AM, Trinition <[email protected]> wrote: > > > > I have a cascading 1:N dictionary mapping from Template to Resource. > > > I'm modifying Template and modifying some of its Resources, calling > > > session.SaveOrUpdate(template) and when session.Transaction.Commit(). > > > > The trouble is, nothing is getting committed! "show_sql" shows the > > > selects, but no INSERTs or UPDATEs. If I debug and inspect > > > session.IsDirty, its false! > > > > What would cause NHibernate to think that nothing is dirty? Are there > > > any further diagnostics steps I can take? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
