Allow for British Postalcodes about publicdb

[153957]

While we're at it, also support other postalcodes.
The longest postalcodes used around the world are about 9 characters long.
So if we support up to 11 or 12 characters, we should be safe.

[kaspervd]

See commit 8997e23 and ec877d6 at the detector_migration branch of publicdb. I have tested migration 0008 on my local copy of the database but somehow I'm not allowed anymore to go to the django administration to confirm the changes.
Apparently the migration resets my password and my admin rights (this happened also during the test of migration 0007, that time Arne made me admin again).

[153957]

Did you set these files up manually, or did you use schemamigration with the --auto flag? http://south.readthedocs.org/en/latest/commands.html#schemamigration

[kaspervd]

Manually, by editing
django_publicdb/inforecords/migrations/0006_contactinformation_fix.py

[153957]

Can you try via the schemamigration route and see if it gives the same results?

[kaspervd]

I've reset the lenghts of the CharFields to 6, 6, 9 and made an initial schemamigration. Then I set the lengths back to 12 and used schemamigration with the --auto flag. This yields the same results (execpt for some comments).
Good to know for future migrations because this is way easier.
Shall I change my version with the one automatically created by schemamigration?

[153957]

If it is the same, then there is no reason to change it.
Perhaps add some of the comments if you deem them useful (if the auto generated added more comments..)

[153957]

Note to self;
Use this to migrate on server:

./manage.py migrate inforecords

[153957]

The migration did not work for me;
_mysql_exceptions.Warning: Data truncated for column 'pobox_postalcode' at row 2

see: ec877d6#commitcomment-3130723

[153957]

fixed by 5ffe8a1