Geoalchemy

Latest version: v0.7.2

Safety actively analyzes 621854 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.7.2

-----

* make BaseFunction work within SQLAlchemy "has" calls. (17, 18, tonio)
* PostGIS: use the "ST_" versions of the GeomFromWKB, GeomFromText, and
isValid functions. This changes breaks compatibility with PostGIS < 1.4
but is a step towards PostGIS 2.0. (19, 20, Phacops)
* Fix incompatibility with SQLAlchemy 0.8.0b2. (27)

0.7.1

-----

* add MANIFEST.in file to include README.rst in source packages. fixes build errors.

0.7

---

* subclass UserDefinedType instead of TypeEngine for GeometryBase (elemoine)
* No longer use "GIST_GEOMETRY_OPS" for PostGIS spatial index creation (6, kwirk)
* Better handling of == and != operators for geometries, PostGIS-only (7, kwirk)
* New wkt_internal option to Geometry constructor, PostGIS-only (9, kwirk)

0.6

---

* support for SQLAlchemy 0.7
* fix errors in the Spatialite implementation of within_distance,

0.5

---

* add within_distance support for MySQL and Spatialite
https://bitbucket.org/geoalchemy/geoalchemy/issue/3/add-within_distance-support
* fix typo in util.py, patch from Roy Hyunjin Han
* fix typos in the documentation, patch from vrutsky
https://bitbucket.org/geoalchemy/geoalchemy/issue/2/typos-in-documentation
* support for table aliases when using RAW ('table_alias.geom_column.RAW')

0.4.1

-----

* DBSpatialElement now working properly for MS SQL Server 2008

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.