Unfortunately, no. Which stinks a bit :) The dialect should be able to override such things.
Suggestion: 1. File a bug report in JIRA. 2. For now, intercept the output from SchemaExporter and fix the syntax using regular expressions. /G 2014-05-13 16:09 GMT+02:00 Richard Walden <[email protected]>: > I'm in the process of creating a custom dialect for a database that we > need to begin supporting. I have the dialect completed and using > nHibernate to generate the schema. However, when it gets to the point to > create the indices, it fails due to the target database having a different > syntax to create index. In ANSI SQL, as you know, the syntax is CREATE > INDEX <index name> ON <table name> (column1, column2, ...). This database > platform syntax is the following: CREATE INDEX <index name> (column1, > column2, ...) ON <table name>. I've asked on nhuser but since I'm a new > poster, they haven't approved my post, so I'm hoping that this group is > more active and will accept this post. My question is, is there a way to > create a new, custom index type that I can put in configuration and use it > versus the default index type. > > Thanks for your help, > > Richard > > -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
