I've found the problem. One of my colleagues had introduced a bug while fixing another concerning his use of an SQL timestamp versioning strategy.
On Nov 10, 8:46 am, Pleb <[email protected]> wrote: > Haven't had much luck with web searches, so I think I'll hit the > source files ;) > > On Nov 9, 7:29 pm, Graham Bunce <[email protected]> wrote: > > > > > I use a SQL generated version so I'm not sure. However, I'm guessing > > you're using the "version" mapping type.This has an option of > > generated="never" (meant to be the default). I'm assuming this means > > let NH do it, not the DB, but I haven't tried it to know for sure. -- 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=.
