Ah, this was the bug my comment on https://bugs.launchpad.net/zope2/+bug/287550 should have applied to. For a buildout recipe it is a very bad idea trying to change the configured values in any way. It should pass them on, in exactly the way you specified them. If the underlying machinery has a problem it should be fixed there.
If you used this patch the following can happen:
1. You specify the storage in mixed case
2. You use this recipe in version A which lower-cases the value automatically
3. Some month pass by
4. You upgrade to a new minor version of Zope
5. Your database connection doesn't work anymore, as someone fixed the problem in Zope
Step 4 here is bad. With your patch an operation that is perceived to be safe, suddenly has a risk to it, which is not documented in the update notes for Zope itself.
The easiest approach for you is to change your storage names to be all lower-case in the first place.
Ah, this was the bug my comment on https:/ /bugs.launchpad .net/zope2/ +bug/287550 should have applied to. For a buildout recipe it is a very bad idea trying to change the configured values in any way. It should pass them on, in exactly the way you specified them. If the underlying machinery has a problem it should be fixed there.
If you used this patch the following can happen:
1. You specify the storage in mixed case
2. You use this recipe in version A which lower-cases the value automatically
3. Some month pass by
4. You upgrade to a new minor version of Zope
5. Your database connection doesn't work anymore, as someone fixed the problem in Zope
Step 4 here is bad. With your patch an operation that is perceived to be safe, suddenly has a risk to it, which is not documented in the update notes for Zope itself.
The easiest approach for you is to change your storage names to be all lower-case in the first place.