<ErrorResponse xmlns=“http://cloudsearch.amazonaws.com/doc/2011-02-01/”> <Error> <Type>Sender</Type> <Code>Throttling</Code> <Message>Rate exceeded</Message> </Error> <RequestId>c753f49e-26b9-11e3-a879-0d3b8f7ade79</RequestId> </ErrorResponse>
Extending Django’s built in user model used to be a tricky affair in Django 1.4 and below. The classic approach was to store additional information in a separate UserProfile model, but you were still stuck with Django’s built in fields. Don’t need the first_name field? Can’t do that. Want to use email address as your username? Also, not possible. Want to enforce unique=True on a value defined otherwise in the Django User model? You’ll need to resort to some hackery using signals.