Patch to fix issue with DatabaseContext

[xylar]

This is preventing pyproj from updating to this version of proj. This, in turn, is tangling up downstream packages.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[xylar]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/proj.4-feedstock/actions/runs/3933391692.

[xylar]

See:
conda-forge/pyproj-feedstock#126
pyproj4/pyproj#1192
OSGeo/PROJ#3497
conda-forge/pyproj-feedstock#129

[xylar]

@snowman2, the patch seems to have worked fine here. Let me know if you have any concerns. If there's an easy way to test if it worked as expected here, I'm happy to add that but if the test is to try to build pyproj, that's also fine with me.

[xylar]

@conda-forge/proj-4, let me know if you have any concerns.

[snowman2]

If there's an easy way to test if it worked as expected here, I'm happy to add that but if the test is to try to build pyproj, that's also fine with me.

I think that testing it with pyproj should be sufficient. I think that there was a test added in the PROJ repo that may be helpful here.

[snowman2]

Thanks @xylar 👍

[xylar]

Thanks for the feedback @snowman2. I looked around and didn't see any obviously related tests added to PROJ but I will freely admit that I don't know my way around very well. I think we can let pyproj be the test.