FDO Database provider performance problem

There was a thread over on the FDO User Mailing list a few weeks ago about PostGIS performance problems

If you follow the thread, there is some discussion of how the provider accesses data, it seems that rather than accessing columns by index, they are accessed by column name which is a lot of overhead (ie string matching).

This is the exacerbated by the select * from table approach used in Mapguide which really slows things down when accessing tables with lots of ADMP metadata columns as used with Autodesk Map.

An easy workaround is to create a view which only contains the columns you need for your layer.