mirror of
https://github.com/SectorLabs/django-localized-fields.git
synced 2025-10-19 14:28:58 +03:00
Compare commits
5 Commits
Author | SHA1 | Date | |
---|---|---|---|
|
476a20ba88 | ||
|
ad99b77bcd | ||
|
151250505d | ||
|
d8b872758c | ||
|
a0ca977cab |
@@ -279,7 +279,7 @@ Besides ``LocalizedField``, there's also:
|
||||
|
||||
Allows storing integers in multiple languages. This works exactly like ``LocalizedField`` except that
|
||||
all values must be integers. Do note that values are stored as strings in your database because
|
||||
the backing field type is ``hstore``, which only allows storing integers. The ``LocalizedIntegerField``
|
||||
the backing field type is ``hstore``, which only allows storing strings. The ``LocalizedIntegerField``
|
||||
takes care of ensuring that all values are integers and converts the stored strings back to integers
|
||||
when retrieving them from the database. Do not expect to be able to do queries such as:
|
||||
|
||||
|
@@ -233,4 +233,4 @@ class LocalizedIntegerValue(LocalizedValue):
|
||||
"""Returns string representation of value"""
|
||||
|
||||
value = self.translate()
|
||||
return str(value) if value is not None else None
|
||||
return str(value) if value is not None else ''
|
||||
|
Reference in New Issue
Block a user