To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() the database level as DEFAULT and CHECK CONSTRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() database level as DEFAULT and CHECK CON- STRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() the database level as DEFAULT and CHECK CONSTRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() the database level as DEFAULT and CHECK CONSTRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() database level as DEFAULT and CHECK CON- STRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() database level as DEFAULT and CHECK CON- STRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 (continues on next

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() database level as DEFAULT and CHECK CON- STRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() the database level as DEFAULT and CHECK CONSTRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: grandma.name = 'Grandma L.' grandma.save() the database level as DEFAULT and CHECK CONSTRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated call to save() will result in an UPDATE rather than another INSERT. The model’s primary key will not change: >>> user.save() # save() returns the number of rows modified. 1 >>> user.id 1 >>> user.save()

To update a row, modify the model instance and call save() to persist the changes. Here we will change Grandma’s name and then save the changes in the database: >>> grandma.name = 'Grandma L.' >>> grandma default isolation level for SQLite databases is None, which equates to autocommit. The reason for this change has to do with some idiosyncracies of pysqlite (or the standard library sqlite3). If you are using the database level as DEFAULT and CHECK CONSTRAINT respectively, but any application change would require a schema change. Because of this, default is implemented purely in python and choices are not validated