Hi Kajar, Yes this is kind of expected behavior. MapGuide will cache schema/class structures to avoid repeated lookups for this info on every render. However if you change the db structure from underneath MapGuide (like through an external db admin tool which I assume is what you are doing), how is MapGuide supposed to know about that if you didn't make the structural changes through only the APIs provided by MapGuide?
Saving any feature source will auto-purge all cached schema/class structures associated with that feature source. So your provided workaround is generally the way to go. - Jackie You wrote: 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
_______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
