-
Notifications
You must be signed in to change notification settings - Fork 826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix PostGIS datasource's schema support #500
Comments
[springmeyer] Mak, thanks and nice catch. As you obv. saw given the 'TODO', I noticed this problem as well and missed following up on it. Shame this was not caught before release as we don't currently plan on a 0.7.1. AFAICT the envelope() method has always failed with custom schema's and the workaround has been to manually set the 'extent' so that the call would be skipped. That should still be possible. Anyway, thanks for the patch, which looks good. Can you imagine other scenarios where we would need to support multiple schemas? I sense proper schema support needs some more thought. |
[springmeyer] Mak, pasting a few of your more complicated queries here that were failing would also be great. I'm currently maintaining a large test suite that I will add them too. Its planned to add this into the nosetests when I can find time. |
[MakKolybabi] Replying to [comment:3 springmeyer]:
They weren't even really queries, just the names of tables: |
[springmeyer] we're going to make a 0.7.1 stable release and will address this issue, so assigning to 0.7.1 milestone |
[springmeyer] fixed in r1631, thanks for the patch Mak! |
My usage of Mapnik uses schemas extensively. I've noticed that the postgis_datasource::envelope() method was throwing errors which caused my renders to fail.
Attached to this ticket will be the quick patch that I made to allow my tiles to render, again.
The text was updated successfully, but these errors were encountered: