I've tried this with HBM mapping files and the result is the same HBM2DDL
only creates one column for the first generator it sees and ignores the
parameters after that. The generator is configured correctly however as it
is trying to get a value from the correct column.
I will probably just have
Note: you have inherited the behaviour of NHibernate.Id.TableGenerator that
mean you should know what the behaviour is.
If you want your own generator you should
implements IPersistentIdentifierGenerator and IConfigurable (if needed) with
all you need for your custom generator.
2009/8/10 Chris
That was what I was wondering. Is this part of the expected behavior of
TableGenerator? It seems to only be an issue with the DDL script
generation. Other than that the TableGenerator functions as I need it to.
I am guessing I need to change something in SqlCreateStrings() and
Hmmm I think I see an idea now, looking at how the Configuration is created
I see how the SqlCreateStrings are called.
What I need is to define a generator with a parameter for AllColumnNames and
then a seperate one for TableName and ColumnName and then use AllColumnNames
to generate the
