Necessary Fixes for PostgreSQL Database Provider

[idseefeld]

Which Umbraco version are you using?

17.3.0-rc.preview.30

Bug summary

This is the next part for issue #20453.

This will be done in three PRs:
#21589
#21590
#21591

After these have been merged I can finalise the Our.Umbraco.PostgreSql and you could install it to use PostgreSQL as database.

It will be tested for the Umbraco CMS without any further packages.

Specifics

No response

Steps to reproduce

All issues that are addressed here occur only in custom database providers like PostgreSQL.
The behaviour for all currently supported database providers must not change.

Expected result / actual result

No response

[github-actions]

Hi there @idseefeld!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂