-
Notifications
You must be signed in to change notification settings - Fork 383
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
add_foreign_key silently does not create foreign keys #656
Comments
@mjc probably ... did some work on 1-3-stable lately please try against it (as well) if possible |
Still does not generate foreign keys on 4679495. I'll try and make a reduced test case today. |
f161ccb may fix this for postgres but it does not fix it for mysql, which is my primary test case. Thanks for responding so quickly though 👍 |
@mjc do not get use to it much ... you had a good timing catching me baking an AR-JDBC release :) please test if you can and let us know if you run into any issues using 1-3-stable |
* 1-3-stable: (43 commits) one last place of missed shared AR4x constants refactoring (thanks travis-ci!) missed places for updating to using shared AR4x constants use the (shared) AR4x constants in PostgreSQL adapter move AR4x constants to (top-level) ArJdbc adapt schema dump test on AR 4.2 ... *t.string \"id\", limit: 255, null: false* now [mysql] bulk compatibility with AR 4.2 - all _sql helper accept an options (hash) [mysql] back-port case sensitive/insensitive comparison [mysql] handle precision for datetimes when doing type_to_sql (AR 4.2 compat) adjust foreign key test introduced in #629 (was failing with MRI under AR 4.2.1) [mysql] schema creation compatibility with AR 4.2 (drop FK & temporayr tables) [mysql] validate_index_length! when available [mysql] foreign key support based on AR 4.2 (fixes #656) review foreign_key support in Postgres adapter (extract helper should be private) AR 4.2 valid_type? method for all finish up the foreign key test - more asserts less puts [postgres] drop_table backported to support `:force => :cascade` option [postgres] foreign_key support back-ported from AR 4.2 (fixes #656) [postgres] primary_key compatibility with latest AR export `open?` and ("raw") `close` helpers on the JDBC connection side alias jdbc_connection active? as valid? (just so its clearer on what it does) ...
I'm working up a test case, but I'm curious if this is expected since 4.2 support is not done yet?
The text was updated successfully, but these errors were encountered: