-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
Fixing #966 #1555
Fixing #966 #1555
Conversation
protected lazy val (pkSyms, softSyms) = syms.toSeq.partition(_.options.contains(ColumnOption.PrimaryKey)) | ||
/* NOTE: pk defined by using method `primaryKey` and pk defined with `PrimaryKey` can only have one, | ||
here we let table ddl to help us ensure this. */ | ||
private lazy val funcDefinedPKs = table.profileTable.asInstanceOf[Table[_]].primaryKeys |
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.
why is asInstanceOf[Table[_]] needed?
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.
Because table.profileTable
was declared as Any
.
Apart from the comment I like it :). Great work. |
I'm curious on the status of this. I was going to try it out with my codebase, but since it's based on 3.2 and won't trivially backport to 3.1 I'm bailing out of that. Is the remaining issue the derby issue? |
Curious about the state of this as well. We used this patch / fork to get around the insertOrUpdate bug. If it's not an issue anymore would love to not need to special-case this. |
@cvogt I'd like to merge it in. |
LGTM. Go ahead, merge :). |
Merged. |
This patch is trying to fix #966 by including
Table.primary(..)
defined primary keys when generating upsert sql.It's not perfect. As the comment said, it remained a derby related issue.
Pls review and give your suggestions.
Thanks!