It turns out there are some exceptions to the rule..Quote source = outward codes against a lookup table I mentioned earlier that the only way to validate a postcode against a lookup table is to use the PAF, which is expensive. But it's much more feasible to just check the outward portion of the code.There are around 3,000 outward codes currently in use - compared to more than 27 million full postcodes.What's more, it's possible to download a list of outward codes.AUPost Code Field as so: from import models from aupostcodes.fields import AUPost Code Field class User Profile(models. postcode = AUPost Code Field() Or, to use the form field directly: from django import forms from aupostcodes.fields import AUPost Code Form Field class Registration Form(forms. postcode = AUPost Code Form Field() Both will ensure appropriate validation.If you see that ostensibly valid post codes are being invalidated, you probably haven't loaded the post codes fixture correctly (see `installation`).
Validating postcodes in T-SQL Given a postcode column within a SQL Server database, here's a T-SQL query that will check the validity of the codes, based on the syntax rules discussed above.These are special codes that have been allocated to very large organisations.They conform to the same syntax rules as other codes, but are independent of any particular geographic area. Country specific validation is supported for most countries including UK, US, Canada, Japan and many others.Note: I haven't tested all combinations of postcodes for the extended country regular expressions.You can find an up-to-date list here."-- End Quote I can see that we code something to validate postcode format taking into account the weird ones mentioned - but you could have a postcode that’s theoretically valid but that doesn’t actually correspond to a real address.