mirror of https://github.com/django/django.git
[3.2.x] Used backend vendors in custom model fields docs.
Backport of d7394cfa13
from main
This commit is contained in:
parent
358e65a5cd
commit
d95a0144e5
|
@ -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
|
||||
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
|
||||
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::
|
||||
|
||||
class MyDateField(models.Field):
|
||||
def db_type(self, connection):
|
||||
if connection.settings_dict['ENGINE'] == 'django.db.backends.mysql':
|
||||
if connection.vendor == 'mysql':
|
||||
return 'datetime'
|
||||
else:
|
||||
return 'timestamp'
|
||||
|
|
Loading…
Reference in New Issue