diff options
| author | Nick Pope <nick.pope@flightdataservices.com> | 2019-03-30 01:49:44 +0000 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2019-03-29 21:50:28 -0400 |
| commit | 5237da3416aa4db47b396e26238db9fdac121c24 (patch) | |
| tree | 4d42c8db1a79f0d2e5e0db500143dcf61ce514ac /docs/howto | |
| parent | 2fb602f58181fa07e416474a35fef1945a6f8df3 (diff) | |
[2.2.x] Removed unnecessary /static from links to PostgreSQL docs.
Backport of 198a2a9381a415f76c3170753270f5087ce4475a from master.
Diffstat (limited to 'docs/howto')
| -rw-r--r-- | docs/howto/custom-model-fields.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index 4bb81611cd..56d5c03718 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -19,7 +19,7 @@ only the common types, such as ``VARCHAR`` and ``INTEGER``. For more obscure column types, such as geographic polygons or even user-created types such as `PostgreSQL custom types`_, you can define your own Django ``Field`` subclasses. -.. _PostgreSQL custom types: https://www.postgresql.org/docs/current/static/sql-createtype.html +.. _PostgreSQL custom types: https://www.postgresql.org/docs/current/sql-createtype.html Alternatively, you may have a complex Python object that can somehow be serialized to fit into a standard database column type. This is another case |