Opened 17 years ago
Closed 12 years ago
#6233 closed Bug (duplicate)
fixture fails to load on inet field
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Core (Serialization) | Version: | 0.96 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Using the admin interface I entered a couple of records for my model.
class TugInstance(models.Model): """This class represents a single instance of TUG in the multi-instance case.""" enabled = models.BooleanField(default=False) public_ip = models.IPAddressField(unique=True) wan_ip = models.IPAddressField(unique=True, blank=True, null=True) lan_ip = models.IPAddressField(unique=True) ready_for_calls = models.BooleanField(default=True) calls_in_progress = models.PositiveIntegerField() default_icp = models.ForeignKey(Icp) def __str__(self): return str(self.id) class Admin: pass
I am using postgresql-7.4.13-2.RHEL4.1 on CentOS 4.4.
I used the json serializer to dump json format of these records.
[root@vmware-espresso teleworker]# cat sample_data.json [{"pk": "1", "model": "top.tuginstance", "fields": {"default_icp": 1, "wan_ip": "", "ready_for_calls": true, "lan_ip": "192.168.1.55", "enabled": true, "public_ip": "216.191.234.111", "calls_in_progress": 5}}, {"pk": "2", "model": "top.tuginstance", "fields": {"default_icp": 2, "wan_ip": "216.191.234.112", "ready_for_calls": true, "lan_ip": "10.33.15.145", "enabled": false, "public_ip": "216.191.234.112", "calls_in_progress": 0}}]
I then cleared the table manually, and tried to load this json as a fixture.
[root@vmware-espresso teleworker]# python manage.py --pythonpath=.. loaddata sample_data.json Loading 'sample_data.json' fixtures... Installing json fixture 'sample_data' from absolute path. Problem installing fixture 'sample_data.json': invalid input syntax for type inet: ""
Seems that there are issues translating the json to sql that postgres will accept.
Change History (9)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Seems to me that the Pg adapter is not accounting for this case correctly, and should be fixed.
I'll see if I can provide a patch.
comment:3 by , 17 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:4 by , 17 years ago
Description: | modified (diff) |
---|
comment:5 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → Bug |
comment:9 by , 12 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Looks like it's the blank=True in the field type. Does this mean that I can't have a blank IPAddressField when using postgres?