Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 do we need that?:)
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.
I am pretty sure that this property would be required to be part of the
credentials
object. As that is what being send to the database driver. Also this seems to only be a problem withhdb
it shouldn't be a problem with@sap/hana-client
. Which would mean that it should probably go into:cds-dbs/hana/lib/drivers/hdb.js
Lines 23 to 41 in 732a2f3
As the change was made in
hdb
to resolve a long running issue. I am hesitant to have our implementation overwrite the default. The main problem with this change is when theHANAService
has a large connection pool or a lot of tenants. As out defaultmax
pool size is10
. It would require ~1000 tenants to reach the reported state in the issue.Additionally it is possible to use the previous
hdb
version which does not have this behavior to achieve the same state as this PR is trying to achieve. Which only becomes a problem when root issue shows up as it would require thehdb
upgrade, but then having it disabled by@cap-js/hana
would not allow CAP applications to connect to their HANA system at all anymore.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.
Agreed that this is the better place. I moved it to
hdb.js
. We could also say we change the default for multitenancy only for now, as there's a higher probability stakeholders will run into issues.For that the internal PR for
cds-mtxs
would be enough, so we don't have to changecds-dbs
at all – keeping this PR in draft state until the DB sync on Monday.