Using postgis databases to store data is one of the great ways to store geodata. In its current version, postgis provides views (http://www.postgresql.org/docs/9.3/static/sql-crea...) which offer great possibilty to GIS users in terms of visualisation and attributes joint.
But in the GIS world, views are not only useful for visualisations but as editing entries directly on the GIS softwares too. The views can have triggers which can write or delete data into tables with some custom rules which are the actual professionnal rules. For example on our project of drinking water network for cities (https://github.com/qwat/QWAT ), we have some triggers on pipes, nodes etc. to ensure information quality and coherency.
This works actually well in production mode, but when it comes to migration from an old system to this one, it would be great to be able to use the FME postgis writer to be more efficient. Actually we worked around and went through sql scripting because writing into views is not possible yet.
Thoughts? Ideas? Proposals?