-
Notifications
You must be signed in to change notification settings - Fork 138
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 --ignore-constraint-names option #167
base: next_release
Are you sure you want to change the base?
Add --ignore-constraint-names option #167
Conversation
Any chance this PR could be looked at? I would find this feature extremely useful. Thanks. |
The command is ignored, but it won't fail.
These options allow to generate PRIMARY KEY and FOREIGN KEY constraints in the CREATE TABLE statement. It currently only works for single column constraints: multicolumn primary keys and foreign keys are still generated separately after the CREATE TABLE statement.
Only generate inline FOREIGN KEY constraints when the target table is in the old schema to avoid referencing non existing tables.
It enables to group multiple "ALTER TABLE" statements for the same table into a single statement.
@jdufresne could you pull it down and try it out for your use case and let us know how it goes? |
I don't see any documentation on building the project. If I missed it, please let me know and I'll try to follow it. I took a guess and ran
|
Ant is correct -- are you on the |
No. I'm on @laurentmartelli's |
@jdufresne this branch might need to be rebased, or atleast have the latest version of develop merged into it. Develop builds fine locally for me -- I haven't tried this branch. Sorry about my other question -- obviously you were on the branch associated with the PR. It's been a long couple of weeks :) |
Just tested, the |
@jdufresne can you merge develop into this branch locally and re-test? |
Auto merge failed so I can't test further. I don't really want to handle the merge by hand as I have no experience with the code base and haven't touched Java in years. If someone else were to rebase or merge the branch I'd happily test the this feature as a user though. |
Thank you for your effort, Jon!
On Wed, Jul 12, 2017 at 9:34 PM Jon Dufresne ***@***.***> wrote:
can you merge develop into this branch locally and re-test?
Auto merge failed so I can't test further. I don't really want to handle
the merge by hand as I have no experience with the code base and haven't
touched Java in years. If someone else were to rebase or merge the branch
I'd happily test the this feature as a user though.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#167 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAmxIpF7jUUsDb9qmsxPixwHW4TtR0tqks5sNXQ6gaJpZM4FwV-w>
.
--
Senior Web Applications Developer
https://chads.website
https://github.com/chadfurman
https://linkedin.com/in/chadfurman
|
We'll need to rebase this branch to solve this feature -- anyone interested in taking this on? |
Le 18/08/2017 12:04, Chad Furman a écrit :
We'll need to rebase this branch to solve this feature -- anyone
interested in taking this on?
Sorry, but I'm over-busy at the moment.
Regards
Laurent
…--
Laurent Martelli // Service Numérique
Tél : 01 80 48 16 14 / 614
|
@laurentmartelli No worries. We'll get this cleaned up at some point :) |
Add --ignore-constraint-names option to compare constraints using only the definition