1 |
|
2004-02-11 Bernhard Herzog <[email protected]> |
2 |
|
|
3 |
|
Handle postgis tables with more than one geometry column. |
4 |
|
|
5 |
|
* Thuban/Model/postgisdb.py |
6 |
|
(PostGISTable._fetch_table_information): Delegate the creation of |
7 |
|
column objects to a different method so that we can extend that in |
8 |
|
derived classes |
9 |
|
(PostGISTable._create_col_from_description): New. Column object |
10 |
|
creation part of _fetch_table_information |
11 |
|
(PostGISShapeStore._create_col_from_description): New. Extend |
12 |
|
inherited method to handle geometry columns |
13 |
|
(PostGISShapeStore.__init__): New parameter geometry_column to |
14 |
|
specify which geometry column to use. Optional but mandatory for |
15 |
|
tables with more than one geometry column |
16 |
|
(PostGISShapeStore._fetch_table_information): Also use the name of |
17 |
|
the geometry column when looking for the srid |
18 |
|
(PostGISShapeStore.ShapeType): Also use the name of the geometry |
19 |
|
column when looking for the shape type |
20 |
|
|
21 |
|
* test/test_save.py (SaveSessionTest.test_save_postgis): Adapt |
22 |
|
NonConnectionStore to changes in the PostGISShapeStore |
23 |
|
|
24 |
|
* test/test_postgis_db.py |
25 |
|
(TestPostGISSpecialCases.test_shapestore_two_geom_cols): Test |
26 |
|
PostGISShapeStore with tables having two geometry columns. |
27 |
|
|
28 |
2004-02-10 Bernhard Herzog <[email protected]> |
2004-02-10 Bernhard Herzog <[email protected]> |
29 |
|
|
30 |
Fix some postgis problems. What remains to be done is real |
Fix some postgis problems. What remains to be done is real |