Ticket #1699 (new enhancement)

Opened 1 year ago

Last modified 3 months ago

postgres: add the ability to specify a list of tables to be treated as layers

Reported by: cph Assigned to: rouault
Priority: normal Milestone: 1.6.0
Component: OGR_SF Version: unspecified
Severity: normal Keywords: postgis postgresql
Cc: warmerdam, project10, mloskot

Description

This functionality is already available for other datasources(as per FrankW). This feature is really needed as it is a huge performance problem when we only want to export 1 table from a system with 100's of tables listed in the geometry_columns table.

Attachments

1699_pg_table_connstr.patch (10.8 kB) - added by project10 on 01/12/08 05:36:01.
patch implementing #1699

Change History

07/13/07 10:26:20 changed by warmerdam

  • keywords set to postgis postgresql.
  • owner changed from warmerdam to mloskot.
  • component changed from default to OGR_SF.
  • cc set to warmerdam.
  • milestone set to 1.5.0.

Mateusz,

I'd like you to add a way of specifying a table list is the PG: connection string. Perhaps an entry like TABLES=name1,name2,... could be allow to establish the set of tables to be scanned. This would need to be removed from the string before the rest is passed on to the postgres connection opening function.

01/12/08 05:36:01 changed by project10

  • attachment 1699_pg_table_connstr.patch added.

patch implementing #1699

01/12/08 05:38:21 changed by project10

This patch allows the list of tables to be specified in the manner Frank suggests. Doing so skips enumeration of the spatial tables from the database metadata.

Includes documentation update and minor documentation style and grammar issue fixes.

01/12/08 05:38:43 changed by project10

  • cc changed from warmerdam to warmerdam, project10.

04/05/08 11:07:58 changed by rouault

  • owner changed from mloskot to rouault.
  • cc changed from warmerdam, project10 to warmerdam, project10, mloskot.

04/05/08 12:07:21 changed by rouault

  • milestone changed from 1.5.1 to 1.6.0.

Patch commited in trunk in r14204 (with minor adaptations related to memory usage).

Is this appropriate for backporting into 1.5 branch ?