p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Used backend vendors in custom model fields docs.

This commit is contained in:
Mariusz Felisiak 2021-08-24 16:16:44 +02:00 committed by GitHub
parent b263f4b69d
commit d7394cfa13
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/howto/custom-model-fields.txt
View File

@ -394,13 +394,14 @@ If you aim to build a database-agnostic application, you should account for
differences in database column types. For example, the date/time column type differences in database column types. For example, the date/time column type
in PostgreSQL is called ``timestamp``, while the same column in MySQL is called in PostgreSQL is called ``timestamp``, while the same column in MySQL is called
``datetime``. You can handle this in a :meth:`~Field.db_type` method by ``datetime``. You can handle this in a :meth:`~Field.db_type` method by
checking the ``connection.settings_dict['ENGINE']`` attribute. checking the ``connection.vendor`` attribute. Current built-in vendor names
are: ``sqlite``, ``postgresql``, ``mysql``, and ``oracle``.
For example:: For example::
class MyDateField(models.Field): class MyDateField(models.Field):
def db_type(self, connection): def db_type(self, connection):
if connection.settings_dict['ENGINE'] == 'django.db.backends.mysql': if connection.vendor == 'mysql':
return 'datetime' return 'datetime'
else: else:
return 'timestamp' return 'timestamp'