[mapguide-users] Help required following up on a FDO PostgreSQL provider bug

[Jackie Ng]

Hi All,

I had some time available to follow up on this FDO bug:

https://trac.osgeo.org/fdo/ticket/1003

However, I am unable to write a failing provider unit test case that can
trigger this problem. The biggest issue is that I do not have a reference
database structure that I can write this test against. The hypothetical
database structures that I came up with could not reproduce this issue.

My tests so far have been using FDO IDescribeSchema with and without
schema/class name filters and verifying that materialized views from other
schemas do not bleed into the schema I am describing, which so far is
always the case.

To whomever is afflicted with this issue, I *require* a minimal database
structure (the CREATE SCHEMA/TABLE/VIEW statements to make this db) and
also ideally steps to reproduce the problem in MapGuide or a FDO client
application like FDO Toolbox.

I will give this ticket 1-2 weeks to live. If I do not receive anything
actionable by then, I will close this ticket as I cannot reproduce the
problem. While I might theoretically know how to fix this issue, I do not
apply theoretical bug fixes. I always want concrete examples to confirm
such issues before fixing them.

- Jackie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20250716/2028741d/attachment.htm>