Open GoogleCodeExporter opened 9 years ago
I have this issue with table names. If I quote the table name in the migration
(e.g.,
"[User]") then it always assumes it doesn't exist (checking if the table exists
before
creating it). If I don't quote the table name, Migrator.NET will detect if the
table
exists and skip the migration, but if it does run the migration, the generated
SQL is
invalid.
Original comment by tgmayfi...@gmail.com
on 27 May 2009 at 6:50
Same problem.
I don't understand why we need logic to determine if a column-name/table-name
needs to be quoted in the first place?
Just quote them all.
Original comment by rasmus.m...@gmail.com
on 28 Jul 2010 at 5:12
What are you doing about this? Have you just given up on this project and moved
on or hacked up the source to work around this? There seems to be a lot of
rough edges and a relatively old release date.
Original comment by cymen...@gmail.com
on 6 Jan 2011 at 5:47
From what I understand, a couple guys (not the original maintainer) did wade
into the Migrator.NET source to get things cleaned up, fixed, and reorganized.
But they ended up doing a complete rewrite and naming it FluentMigrator. You
can hear the full history on a Herding Code episode:
http://herdingcode.com/?p=233
What I've done to bypass most of the trouble caused by keywords was to create a
custom dialect (in my case, derived from SqlServerDialect) that overrides
ColumnNameNeedsQuote and TableNameNeedsQuote so they both give "true".
Original comment by tgmayfi...@gmail.com
on 6 Jan 2011 at 4:56
I'll go check that out. Thanks!
Original comment by cymen...@gmail.com
on 6 Jan 2011 at 5:27
Original issue reported on code.google.com by
paul.dhe...@gmail.com
on 26 May 2009 at 2:09