Hi Phil,
If your view is large, you will get sluggish performance with QGIS. One
solution is a materialised view, which is not directly supported in Postgres,
but can be made to work. This does create a physical table representing the
view, which can have appropriate indexes applied.
The issue
On Thu, Sep 15, 2011 at 11:25:52PM +0200, Andreas Forø Tollefsen wrote:
> Hi all,
>
> Trying to do a populate_geometry_columns(); but it does not work.
> This is PostGis 2.0 with Gdal 1.8, Geos 3.4
Revision number ?
> Command: SELECT Populate_Geometry_Columns();
> ERROR: query string argument o
I am trying to create a view that can be opened in Quantum using
ST_INTERSECTION. This returns multiple entries for the same road object and
therefore Quantum refuses to use the GID field as it is not unique. As an
alternative I thought to use row_number but this is a bigint and Quantum says
Hi Edward,After several days of fighting with the data we finally managed to get the desired results. I followed your recipe. On step 3 however I have seen that ST_Intersects doesn't work any more between de UNION'ed and source data. Although most objects are on top of each other ST_Intersects rema
