pub/django-localized-fields
1
0
Fork 0
mirror of https://github.com/SectorLabs/django-localized-fields.git synced 2025-04-24 19:32:53 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #60 from AdrianMuntean/error_on_empty_localized_integer_field

Browse Source 
Return empty string in case the LocalizedIntegerField is null
This commit is contained in:
Swen Kooij 2019-02-21 12:31:50 +02:00 committed by GitHub
commit 151250505d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -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:

2
localized_fields/value.py
View File

@ -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 ''