Level 53
@caje731 http://laravel.com/docs/5.0/schema#adding-columns
$table->enum('operation_type', ['create', 'update', 'delete']);
However I would rather do it at the code level, not necessarily in the db.
4 likes
Mar 18, 2015
5
Level 1
Restricting column values while creating a table using migration
Hi,
I'm trying to create a table using a migration, and I would like to restrict values of a column 'operation_type' to either of 'update', 'create', 'delete' . Can this be done while defining the migration? More importantly, is this the right way of restricting values ?
Level 55
Why would you not want to do it in the DB? Surely having it at the Database level will absolutely not allow any other values. Just like setting unique on a table prevents multiple occurrences of the same value.
I'd still do it at the code level too, but why not both?
Level 53
@mstnorris Because most likely db is treated somewhat as a static (in terms of the schema) storage. Once setup, it rather does not change. However the needs of your app may change, and you reflect the change in your logic.
That said, you need to alter the behaviour of the app, but do not need to touch the db.
This is matter of preference and needs. I would say it depends on the way an application is developed and how big/complex it is. If you need that additional layer of control, then use both, but mind that you also need to take care of the errors handling then (unique, enum, fk or other constraints)
1 like
Level 13
Where and how would you do this at the code level? @mstnorris @jarektkaczyk
Level 1
@bahuzi I would suggest using a mutator:
// restrict the user_type attribute to only 'user' or 'admin'
public function setUserTypeAttribute($value)
{
$this->attributes['user_type'] = in_array($value, ['user', 'admin']) ? $value : 'user';
}
(works in laravel 9)
Please or to participate in this conversation.