summaryrefslogtreecommitdiff
path: root/docs/howto
diff options
context:
space:
mode:
authorMarti Raudsepp <marti@juffo.org>2016-10-25 18:43:32 +0300
committerTim Graham <timograham@gmail.com>2016-10-25 11:43:54 -0400
commitae91fc786cc2d93a325a940f0ead77d00cb42a17 (patch)
tree8cbecab0639ab8d921af19f32d6f30bdf4df0ff6 /docs/howto
parent3a416e4ba9f7094be55110dae8e5a6451984d226 (diff)
[1.10.x] Updated postgresql.org links to https and made them canonical.
Backport of 51fbe2a60d9c7ff3fe62688ad262ccda648f506d from master
Diffstat (limited to 'docs/howto')
-rw-r--r--docs/howto/custom-model-fields.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt
index 0c26d2ca5d..3c71f8f004 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: http://www.postgresql.org/docs/current/interactive/sql-createtype.html
+.. _PostgreSQL custom types: https://www.postgresql.org/docs/current/static/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