diff options
| author | Ville Skyttä <ville.skytta@iki.fi> | 2016-10-07 13:20:24 +0300 |
|---|---|---|
| committer | Ville Skyttä <ville.skytta@iki.fi> | 2016-10-08 20:42:50 +0300 |
| commit | e5a063a87ce50552cb451075386563a38a7e2666 (patch) | |
| tree | eb88021f5466c05ceef34dd387a84c49c11de883 | |
| parent | 8c2c464cb8e1b40f90f544295afbf9a83b372eb7 (diff) | |
| download | sqlalchemy-e5a063a87ce50552cb451075386563a38a7e2666.tar.gz | |
spelling: Postgis -> PostGIS
| -rw-r--r-- | doc/build/changelog/changelog_08.rst | 2 | ||||
| -rw-r--r-- | doc/build/core/custom_types.rst | 4 | ||||
| -rw-r--r-- | examples/postgis/postgis.py | 4 |
3 files changed, 5 insertions, 5 deletions
diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst index ba5e64e8c..6eb58306a 100644 --- a/doc/build/changelog/changelog_08.rst +++ b/doc/build/changelog/changelog_08.rst @@ -3189,7 +3189,7 @@ to augment bind- and result- behavior at the SQL level, as opposed to in the Python level. Allows for schemes like transparent encryption/ - decryption, usage of Postgis functions, etc. + decryption, usage of PostGIS functions, etc. .. change:: :tags: feature, sql diff --git a/doc/build/core/custom_types.rst b/doc/build/core/custom_types.rst index cbcc8c226..f47640c92 100644 --- a/doc/build/core/custom_types.rst +++ b/doc/build/core/custom_types.rst @@ -338,7 +338,7 @@ possible to define SQL-level transformations as well. The rationale here is whe only the relational database contains a particular series of functions that are necessary to coerce incoming and outgoing data between an application and persistence format. Examples include using database-defined encryption/decryption functions, as well -as stored procedures that handle geographic data. The Postgis extension to PostgreSQL +as stored procedures that handle geographic data. The PostGIS extension to PostgreSQL includes an extensive array of SQL functions that are necessary for coercing data into particular formats. @@ -348,7 +348,7 @@ can include implementations of when defined to return a non-``None`` value should return a :class:`.ColumnElement` expression to be injected into the SQL statement, either surrounding bound parameters or a column expression. For example, to build a ``Geometry`` -type which will apply the Postgis function ``ST_GeomFromText`` to all outgoing +type which will apply the PostGIS function ``ST_GeomFromText`` to all outgoing values and the function ``ST_AsText`` to all incoming data, we can create our own subclass of :class:`.UserDefinedType` which provides these methods in conjunction with :data:`~.sqlalchemy.sql.expression.func`:: diff --git a/examples/postgis/postgis.py b/examples/postgis/postgis.py index 01671c5c4..ffea3d018 100644 --- a/examples/postgis/postgis.py +++ b/examples/postgis/postgis.py @@ -130,8 +130,8 @@ class LineString(Curve): # DDL integration -# Postgis historically has required AddGeometryColumn/DropGeometryColumn -# and other management methods in order to create Postgis columns. Newer +# PostGIS historically has required AddGeometryColumn/DropGeometryColumn +# and other management methods in order to create PostGIS columns. Newer # versions don't appear to require these special steps anymore. However, # here we illustrate how to set up these features in any case. |