Adrian,
On 01/11/2012 04:32 PM, Adrian Klaver wrote:
> Would seem that they both have the same issue, namely pulling over the table
> names and the meta data is resource intensive.
The problem is that the slow part is the "connect", just at the ***** in
the in-line comment :-)
> 4.2.2. Loading a PostGIS Layer
>
> Once you have one or more connections defined, you can load layers from the
> PostgreSQL database.
> Of course this requires having data in PostgreSQL. See Section 4.2.4 for a
> discussion on importing data into
> the database.
> To load a layer from PostGIS, perform the following steps:
> – If the Add PostGIS Table(s) dialog is not already open, click on the Add
> PostGIS Layer toolbar button.
> – Choose the connection from the drop-down list and click Connect .
*******
> – Select or unselect Also list tables with no geometry
> – Optionally use some Search Options to define which features to load from the
> layer or use the
> Build query icon to start the Query builder dialog.
>
> ^^^^^^^^^^^^^^^
> Wonder if it would be possible to restrict the dataset(tables) by using the
> above?
Thanks for your feedback anyway, this helps clarifying the issue.
Cheers
Kirill
--
_________________________________________________
ETH Zürich
Institute for Transport Planning and Systems
HIL F 32.2
Wolfgang-Pauli-Str. 15
8093 Zürich
Phone: +41 44 633 33 17
Fax: +41 44 633 10 57
Secretariat: +41 44 633 31 05
E-Mail: kirill.mueller@ivt.baug.ethz.ch