From ae91fc786cc2d93a325a940f0ead77d00cb42a17 Mon Sep 17 00:00:00 2001 From: Marti Raudsepp Date: Tue, 25 Oct 2016 18:43:32 +0300 Subject: [1.10.x] Updated postgresql.org links to https and made them canonical. Backport of 51fbe2a60d9c7ff3fe62688ad262ccda648f506d from master --- docs/howto/custom-model-fields.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/howto') 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 -- cgit v1.3