We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think this is due the EclipseLink orm replace of hibernate orm process casue
Apply Failed! Exception [EclipseLink-4002] (Eclipse Persistence Services - 4.0.2.v202306161219): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: org.h2.jdbc.JdbcSQLSyntaxErrorException: Syntax error in SQL statement "SELECT id, collector, creator, gmt_create, gmt_update, modifier, monitor_id FROM hzb_collector_monitor_bind WHERE (monitor_id IN [*]?)"; expected "("; SQL statement: SELECT id, collector, creator, gmt_create, gmt_update, modifier, monitor_id FROM hzb_collector_monitor_bind WHERE (monitor_id IN ?) [42001-224] Error Code: 42001 Call: SELECT id, collector, creator, gmt_create, gmt_update, modifier, monitor_id FROM hzb_collector_monitor_bind WHERE (monitor_id IN ?) bind => [1 parameter bound] Query: ReadAllQuery(referenceClass=CollectorMonitorBind sql="SELECT id, collector, creator, gmt_create, gmt_update, modifier, monitor_id FROM hzb_collector_monitor_bind WHERE (monitor_id IN ?)")
update success.
HertzBeat version(s): master code
No response
The text was updated successfully, but these errors were encountered:
see https://stackoverflow.com/questions/12758424/eclipselink-how-to-use-empty-collection-in-in-operator
Sorry, something went wrong.
tomsun28
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Current Behavior
I think this is due the EclipseLink orm replace of hibernate orm process casue
Expected Behavior
update success.
Steps To Reproduce
Environment
Debug logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: