errors generating schema_migration model about xo HOT 4 CLOSED

Oh -- interesting -- yeah, typically schema migration tables do a pretty bad design in general by having only one field as a unique key, which is the cause of the problem here, as the current templates assume the primary key is being managed by the database.

Don't get me started on why this is a horrible design for a table!

The answer here, I think, is to finish the include/exclude options that I have been working off, but have delayed finishing in the interest of getting the databases all to a minimum feature set.

xo is fairly dumb/naive, and these kinds of cases will show that. It's definitely in the interest though that it be smarter about such conditions. I just need to think a bit about how I want to support this out of the box.

from xo.

Include/exclude sounds like a good option. Thanks again for the neat code gen.

from xo.

I created a temporary workaround for this, but will likely revisit the logic added in this commit at a later date.

xo should now work, "as expected" for tables with only one field that is the primary key.

from xo.

Confirmed. Thanks!

from xo.