Created
June 8, 2017 15:34
-
-
Save sebersole/aecb1af4d231578b5ffb0b230c0887df to your computer and use it in GitHub Desktop.
proposed MultiTableBulkIdStrategy changes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
interface UpdateHandler { | |
// todo (6.0) : Ideally I think the best option is for this delegate to just handle execution of the "entire SQM delete" | |
// i.e. the single HQL that needs to get split into multiple SQL operations... | |
// | |
// something like: | |
/** | |
* Execute the multi-table update indicated by the SQM AST passed in when this | |
* UpdateHandler was created. | |
* | |
* @param parameterBindings The value for all query parameter bindings | |
* @param session The originating Session | |
* | |
* @return The "number of rows affected" count | |
* | |
* @see #buildUpdateHandler | |
*/ | |
int execute(QueryParameterBindings parameterBindings, SharedSessionContractImplementor session); | |
// What is the proper return type? for now returning the "number of rows affected" count.. | |
// Similarly, any other parameters to pass? | |
// the parameter references in the tree still just refer back the the overall bindings | |
// regardless of which "split tree" they get split into. Perfect! :) | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment