When opening a database, it's name should be specified in the form
"PG:dbname=
Currently all regular user tables are assumed to be layers from an OGR
point of view, with the table names as the layer names. Named views are
not currently support.
Regular (non-spatial) tables can be accessed, and will return features with
attributes, but not geometry. If the table has a "wkb_geometry" field, it will
be treated as a spatial table. The type of the field is inspected to
determine how to read it. It can be a PostGIS geometry field, which
is assumed to come back in OGC WKT, or type BYTEA or OID in which case it
is used as a source of OGC WKB geometry.
If there is an "ogc_fid" field, it will be used to set the feature id of
the features, and not treated as a regular field.
Currently there is no support for coordinate systems in the PostgreSQL driver.
As mentioned above the type system is impoverished, and many OGR types
are not appropriate mapped into PostgreSQL.
Currently only sequential writing is supported.
If the database has PostGIS types loaded (ie. the geometry type) newly
created layers will be created with the PostGIS Geometry type. Otherwise
they will use OID.
Caveats
Creation Issues
The PostgreSQL driver does not support creation of new datasets (a database
within PostgreSQL), but it does allow creation of new layers within an
existing database.Dataset Creation Options
NoneLayer Creation Options
See Also