-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First steps towards AR 5 support on Postgres #12
Conversation
Most of the failures for Postgres look like this:
Those are caused by the inline |
SchemaDump::Table::Column.new name: m[:name], type: m[:type], options: eval("{" + m[:options] + "}"), comments: [] | ||
} | ||
if m.nil? | ||
env.table.statements << statement |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the t.index
statement will actually need to be parsed and turned into a SchemaDump::Table::Index
instance (or something similar that outputs a new t.index
string). Not sure whether it makes sense to add it to env.table.statements
or have something like env.table.indexes
.
The Regarding Thanks again! |
Or 30b2f09 for that matter |
I've dropped 180875f from this PR I'll open an issue to discuss |
Also includes an update to the version range to limit to AR < 6 (cf. SchemaPlus/schema_monkey#11) as well as some updates to the specs that relate to the order that AR 5 returns columns for polymorphic references.