SQLite Doesn’t Care About Your max_length

SQLite databases don’t care about your using of max_length on your models. Let’s look at an example.


class Book(models.Model):
    title = models.CharField(max_length=30)

Now, we’ll run some queries.

$ ./manage.py makemigrations
$ ./manage.py migrate
$ ./manage.py shell
>>> from book.models import Book
>>> title = 'A' * 31
>>> print len(title)
>>> book = Book.objects.create(title=title)
>>> book.save()
>>> len(book.title)

When running SQL queries using SQLite, you find that you can create records and the database will save a CharField with attributes with bigger strings than what the max_length describes.

Is there any way we can fix this? Sure there is!

One way that we can validate if our model instance is correct is to run a method called full_clean().

So, what we can do is override our save() method so that we can validate our SQLite model before we save our model. Let’s take a look.

class Book(models.Model):
    title = models.CharField(max_length=10)

    def save(self, *args, **kwargs):
            super(Book, self).save(*args, **kwargs)
            print "Error saving model"

As you can see, if self.full_clean() throws an error, our instance will print out ‘Error saving model’ and our save method will not save our record to the database.

Try this out next time you use SQLite for your database.

I hope that works for you!


Struggle with the Django Documentation?

If this post helped you, sign up for my newsletter and you'll get a new post each week that will help you master Django ABSOLUTELY FREE!

Powered by ConvertKit