BinaryBlob is used for anything, that type need to be IUserVersionType and it is needed only by MsSQL.IMO its place is NH-Contrib NHibernate.UserTypes.SqlTypes
2009/4/13 Ayende Rahien <[email protected]> > Is there a reason that we require a custom user type? > It seems to me that we should be able to do this using just BinaryBlob. > > > > On Mon, Apr 13, 2009 at 11:58 PM, Fabio Maulo <[email protected]>wrote: > >> If I well remember we have a specific test about this matter.... >> minute....found NHibernate.Test.VersionTest.Db.MsSQL >> it are using sql-type="timestamp" and a custom IUserVersionType >> >> If you are writing an example you can link the code >> >> http://nhibernate.svn.sourceforge.net/viewvc/nhibernate/trunk/nhibernate/src/NHibernate.Test/VersionTest/Db/MsSQL/BinaryTimestamp.cs?revision=4111&view=markup >> >> >> >> 2009/4/13 Ayende Rahien <[email protected]> >> >> I am trying to use SQL Server timestamp with the following mapping: >>> >>> <version name="Version" >>> column="Version" >>> generated="always" >>> unsaved-value="null" >>> type="BinaryBlob"/> >>> >>> >>> The problem is that it generate the following SQL on update: >>> UPDATE People >>> SET Version = 'System.Byte[]' /* @p0 */, >>> Name = 'other' /* @p1 */ >>> WHERE Id = 1 /* @p2 */ >>> AND Version = 'System.Byte[]' /* @p3 */ >>> >>> I am pretty sure that there is a mistake here somewhere, but I am not >>> sure if this is my bug or not. >>> >> >> >> >> -- >> Fabio Maulo >> > > -- Fabio Maulo
