Greetings,
* Stephen Frost (sfrost@snowman.net) wrote:
> * Frank van Vugt (ftm.van.vugt@foxi.nl) wrote:
> > Well, I didn't run into this issue with any of my db's that 'nicely' use
> > tables in various schema's, it was actually the one 'older' db with everything
> > in the public schema that brought it up, so maybe keeping one of those around
> > isn't too bad an idea ;)
>
> Yeah, I'll be including this in a regression test also, to make sure we
> don't end up breaking this special case again in the future.
I've now pushed a fix for this, would be great to know if it solves your
issue.
Thanks!
Stephen
