| 1 |
2004-03-12 Bernhard Herzog <[email protected]> |
2004-03-12 Bernhard Herzog <[email protected]> |
| 2 |
|
|
| 3 |
|
Support views in addition to normal tables in the postgis |
| 4 |
|
shapestore |
| 5 |
|
|
| 6 |
|
* Thuban/Model/postgisdb.py |
| 7 |
|
(PostGISShapeStore._fetch_table_information): Add a fallback for |
| 8 |
|
the case where the table name is not in the geometry_columns |
| 9 |
|
table. This is usually the case for views. Also, set |
| 10 |
|
self.shapestore here. |
| 11 |
|
(PostGISShapeStore.ShapeType): No need to query the database all |
| 12 |
|
the time. The shape type is now determined in |
| 13 |
|
_fetch_table_information |
| 14 |
|
|
| 15 |
|
* test/postgissupport.py (PostgreSQLServer.new_postgis_db) |
| 16 |
|
(PostgreSQLServer.get_static_data_db, PostGISDatabase.__init__): |
| 17 |
|
New parameter to specify views. |
| 18 |
|
(PostGISDatabase.has_data): Also compare the views. New views |
| 19 |
|
parameter |
| 20 |
|
(PostGISDatabase.initdb): Create the views. |
| 21 |
|
(PostgreSQLServer.get_default_static_data_db): Add the v_landmarks |
| 22 |
|
view |
| 23 |
|
|
| 24 |
|
* test/test_postgis_db.py |
| 25 |
|
(TestPostGISShapestorePointFromViews): New. Test a |
| 26 |
|
PostGISShapeStore with a view |
| 27 |
|
(TestPostGISShapestorePointOIDAsGIDColumn.setUp): Pass the name of |
| 28 |
|
the geometry_column explicitly to test whether that works |
| 29 |
|
|
| 30 |
|
2004-03-12 Bernhard Herzog <[email protected]> |
| 31 |
|
|
| 32 |
Final step for explicit id/geometry columns: Loading and saving |
Final step for explicit id/geometry columns: Loading and saving |
| 33 |
|
|
| 34 |
* Resources/XML/thuban-1.1.dtd: New. Derived from thuban-1.0.dtd |
* Resources/XML/thuban-1.1.dtd: New. Derived from thuban-1.0.dtd |
Parent Directory
| 
Revision Log
| 
Patch