The Caching of the database connection is the issue. Workarounds: 1. Restart MapGuide Server 2.Redifine Data Connection and re-save 3. Step 2 plus re-point the layer back to the Data Connection to see changes to the database.
On Fri, Apr 11, 2025 at 8:46 AM Scott Hameister via mapguide-users < [email protected]> wrote: > Happens with SQL as well. Also happens with empty tables (electric > outages) if a reboot occurs, can also get messed up by bad views. It seems > a schema snapshot occurs at startup, or refreshing of data source. Makes > some sense since it would be a big time waste to check schema at every > redraw > > On Fri, Apr 11, 2025, 7:25 AM Kajar Kuldsepp via mapguide-users < > [email protected]> 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 >> > _______________________________________________ > mapguide-users mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/mapguide-users >
_______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
