Yes, that is a bug that I'm fixing as part of https://github.com/Particular/NServiceBus.NHibernate/pull/28
This fix will be going out very soon.
I'm sorry for the inconvenience, but for now the only workaround is to generate the TSQL from whatever is currently created and then manually update the schema and redo the tables.