[mapguide-users] Trouble with layer using Postgresql data

[Kajar Kuldsepp]

Hi!
There have been issue for a years with layers based the Postgresql table
data.
No matter which Postgresql version or mapguide version I have used, for me
it have been always issue.
Problem: layer becomes invisible, when Postgresql schema structure will
change(new table have created). For a sample I have table A under public
schema, which is source of Mapguide layer. Now I create table B in public
schema and this will make layer consuming table A data invisible on the
map.
I use built in Postgresql provider to create feature source.
I found workaround for that issue: when layer become invisible I have to
use Maestro and open that Postgresql feature source and just save it again
and this will fix the issue.
Does anyone else experience similar behavior and how to fix it?

Kajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20250411/70bc977b/attachment.htm>