Description
Environment
Activity
Anthony Dewhirst February 6, 2012 at 12:15 PM
I agree with the comments that this should be fixed within the SchemaExport tool, but as it looks like this might not happen, I have created a solution along Fabio's solution for ConfORM for Fluent NHibernate here:
http://www.anthonydewhirst.blogspot.com/2012/02/fluent-nhibernate-solution-to-enable.html
Sukh September 19, 2011 at 4:00 PM
I bumped into this issue myself today, and I would agree with Ricardo. If the Schema Export creates the HiLo table partially, yet only counts the final column name, surely that's a bug? Either it should create the whole table correctly or leave the entire table to be created manually?
Ricardo Peres May 4, 2011 at 4:29 AM
Fabio,
But this is part of the standard HiLo generator, it is not a new feature to be implemented on a custom generator.
Shouldn't it be the responsible for the creation of these additional columns?
Thanks,
RP
Fabio Maulo May 4, 2011 at 4:12 AM
Custom additional columns should be managed by you or your custom generator.
An example is available here.
http://code.google.com/p/codeconform/source/browse/ConfOrm/ConfOrm.UsageExamples/HighLowPerEntity/Demo.cs
Please use the nhusers list for questions.
The SchemaExport class, when creating a table for the HiLo algorithm, does not take in consideration any eventual columns specified as its parameters.
For example, if an entity is using a parameter defined as:
<param name="column">MyEntityColumn</param>
It should create table hibernate_unique_key with an additional MyEntityColumn column, but it does not.