Opened 16 years ago
Closed 16 years ago
#10114 closed (invalid)
spaces are inserted for 'blank' fields
Reported by: | wmstudio | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.0 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
I have a model in which several fields are specified as follows:
lat_dec = models.FloatField(blank=True, null=True) lon_dec = models.FloatField(blank=True, null=True) lat_dms = models.CharField(max_length=9, blank=True, null=True) lon_dms = models.CharField(max_length=10, blank=True, null=True)
In case of the CharFields, spaces are inserted into the database (PostgreSQL) when in the admin form the entry-fields are left blank. I found that out because I made some trigger procedures which update lat_dec and lon_dec when lat_dms and lon_dms (see model) are specified and vice versa. Now I made a workaround by adjusting the trigger procedure so it sets the fields to NULL when containing only spaces.
Change History (2)
comment:1 by , 16 years ago
Description: | modified (diff) |
---|
comment:2 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
The admin strips leading and trailing spaces, so I don't quite see how this would be happening, and sure enough I can't reproduce this. Please investigate further to make sure it's not a bug in your own code, and reopen if you can provide more details to help us track this down.
(reformatted description)
Do these values stored in the database really contain space(s)? How many of them? Or are they empty strings?