I can't remember if it was you who I replied to in another thread, but have you ever had byte[] working with a version column? (Outside of Fluent...) The NH docs state this: "Version numbers may be of type Int64, Int32, Int16 , Ticks, Timestamp, or TimeSpan (or their nullable counterparts in .NET 2.0)."
Which leads me to think a byte[] wouldn't work, but perhaps I'm wrong. On Wed, Aug 26, 2009 at 5:58 PM, Corey Coogan <[email protected]> wrote: > > Now that I've sorted out all my post 1.0RC issues, I'm back to > figuring out my strategy for mapping a Timestamp : byte[] column to a > Version mapping for concurrency. > > Prior to 1.0RC, I could use the IClassMap property that came from the > IClassConvention. This was nice because I could setup the mapping to > the Timestamp column on my entity base class, which included > attributes and other settings. > > I'm using both ClassMap<T> and automapping, so I don't want to create > a base map file if I can avoid it. Any idea how I can accomplish this > in 1.0RC? The IVersionConvention doesn't get me what I need as I > can't specify the Access method of the property or define custom > attributes or specify my SqlType. > > Any ideas how to accomplish this? > > THanks, > corey > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
