summaryrefslogtreecommitdiff
path: root/__init__.py
diff options
context:
space:
mode:
authorDan McGee <dan@archlinux.org>2010-05-24 10:57:17 -0500
committerDan McGee <dan@archlinux.org>2010-05-24 10:57:17 -0500
commit5adceb6586afcac163b1abf9fb6f2d0f1b151b9a (patch)
treee62069f0b0b1d649bf5470ae2d6db11919e0723f /__init__.py
parenta1f7520b8cf35e134aed6b8d7933e2ccf82a2b50 (diff)
Fix null field issues exposed by Django 1.1.2
Apparently Django 1.1.1 let null fields pass right through but this now causes reporead to blow up in 1.1.2. Fix the issue and get things working again by allowing nulls where it probably makes sense and including a migration to fix the issue, which for the real database will be a no-op. Signed-off-by: Dan McGee <dan@archlinux.org>
Diffstat (limited to '__init__.py')
0 files changed, 0 insertions, 0 deletions