You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we're executing the content of the database schema resources in one go (via JdbcOperations.execute(…), which is only intended to execute a single statement). Some databases like HSQLDB cannot properly deal with strings containing multiple statements at once.
We should move to ResourceDatabasePopulator to actually submit the statements contained in the schema files individually.
The text was updated successfully, but these errors were encountered:
We now use ResourceDatabasePopulator to execute the schema files creating the infrastructure for the event publication registry. This makes sure that the statements in those files are executed individually.
Related ticket: GH-403.
Added indexes for HSQLDB (after fix for GH-507). Removed by-listener index for MySQL as it would not be used anyway. Polished index names. Disable Spring Boot banners in tests.
Original pull request: GH-411.
Currently, we're executing the content of the database schema resources in one go (via
JdbcOperations.execute(…)
, which is only intended to execute a single statement). Some databases like HSQLDB cannot properly deal with strings containing multiple statements at once.We should move to
ResourceDatabasePopulator
to actually submit the statements contained in the schema files individually.The text was updated successfully, but these errors were encountered: