Hi, Creating these two will trigger issue. Materialized views can be in public schema.
Create materialized view mv_test1 as select 1 as foo; Create materialized view mv_test2 as select 2 as foo; Br, Ari ke 16. heinäk. 2025 klo 16.10 Jackie Ng via mapguide-users < mapguide-users@lists.osgeo.org> kirjoitti: > 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 > _______________________________________________ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapguide-users >
_______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
