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

[Jackie Ng]

In the interest of maximum transparency as to what I'm doing, this is my
unit test.

I run these SQL statements on an empty database:

CREATE TABLE vec (id INTEGER PRIMARY KEY, a INTEGER, b INTEGER);
CREATE VIEW vec_view AS SELECT * FROM vec;
CREATE MATERIALIZED VIEW hypot AS SELECT id, sqrt(a*a + b*b) as c FROM vec;
CREATE MATERIALIZED VIEW squared AS SELECT id, pow(a, 2) as c, pow(b, 2) as
d FROM vec;
CREATE SCHEMA Foo;
CREATE TABLE Foo.vec2 (id INTEGER PRIMARY KEY, a INTEGER, b INTEGER);
CREATE VIEW Foo.vec_view2 AS SELECT * FROM Foo.vec2;
CREATE MATERIALIZED VIEW Foo.hypot2 AS SELECT id, sqrt(a*a + b*b) as c FROM
Foo.vec2;

This results in a database with the following schema/tables/views

   - public
      - vec [table]
      - vec_view [view]
      - hypot [mat view]
      - squared [mat view]
   - Foo
      - vec2 [table]
      - vec_view2 [view]
      - hypot2 [mat view]

I then proceed to run the following tests:

1. Describe the full schema. I expect each schema to be present and each
table/view/matview under it is a class definition. Each column is a data
property on their respective class.

Expectations: correct

2. Describe a partial schema with a schema hint of "public" and a class
name hint of "hypot". I expect it to contain only one schema (public) with
one class (hypot). Each column from the hypot view is present in the class
as a data property.

Expectations: correct

What am I possibly missing here? No class definitions are being misplaced
in other schemas.

- Jackie



You wrote:

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20250718/60c81810/attachment.htm>