Skip to content

Conversation

@rPraml
Copy link
Collaborator

@rPraml rPraml commented Apr 17, 2025

When a config is loaded with loadSettings from different places or using setDefaults, the behaviour of customProperties/clientInfo/initSql is not consistent

setDefaults did not honor clientInfo / initSql at all.

multiple loadSettings should merge customProps/clientInfo/initSql Old behaviour:

  • initSql is always overwritten
  • customProps are overwritten, if value is present in config (even if it was empty)
  • clientInfo is only overwrtitten when configured in properties

New behaviour:

  • all of them are merged. So multiple loadSettings will append initSql or put all props to clientInfo/customProps

btw: initSql also supports "delimiter $$"

rPraml added 2 commits April 17, 2025 09:14
…ltiple places

When a config is loaded with loadSettings from different places, the
behaviour of customProperties/clientInfo/initSql is not consistent

setDefaults did not honor clientInfo / initSql at all.

multiple loadSettings should merge customProps/clientInfo/initSql
Old behaviour:
- initSql is always overwritten
- customProps are overwritten, if value is present in config
  (even if it was empty)
- clientInfo is only overwrtitten when configured in properties

New behaviour:
- all of them are merged. So multiple loadSettings will append initSql
  or put all props to clientInfo/customProps

btw: initSql also supports "delimiter $$"
@rbygrave rbygrave added this to the 9.6 milestone Apr 23, 2025
@rbygrave rbygrave merged commit 5a5bb5e into ebean-orm:master Apr 23, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants