-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
Allow existing models in eager/flat create #199
Allow existing models in eager/flat create #199
Conversation
travis is aggravating... |
Going a different way with this now. (Just to document this in public and give an update.) |
9217659
to
b80faa0
Compare
Think it's good to go now! |
* [Fix] issue when using IN more than once '?' wildcards * slices with in
* The lastest docs are on the website, and keeping them here mislead users. * Let's use SHOULDERS here too!
…#271) * improved cockroach configuration and fixed bugs on connection details * oops! didn't remove debugging log * bugfix: blank argument also affect as argument, in secure mode
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.
Sorry for the delay, here are some points to fix first. :)
c3a3175
to
f2e5783
Compare
... and now I'm going to fix this rebase mess... |
* [Fix] issue when using IN more than once '?' wildcards * slices with in
* The lastest docs are on the website, and keeping them here mislead users. * Let's use SHOULDERS here too!
…#271) * improved cockroach configuration and fixed bugs on connection details * oops! didn't remove debugging log * bugfix: blank argument also affect as argument, in secure mode
* Deprecate Left and Right InnerJoins in favor of one InnerJoin. * Add oncer Deprecation notices to LeftInnerJoin and RightInnerJoin
b23bb3e
to
b34a968
Compare
b34a968
to
151a1b4
Compare
Allows use of existing objects which will update them instead of duplicating them.
WARNING: this will overwrite an object to be empty for fields that are missing currently. Would love input as to how people would like to handle this... if exists just create association? only update if valid? leave it to the user of the library with a strong warning? (In my mind this is the only reason it's WIP and not done)