I would say the same. It is about team size: If you are alone and don't care whether your client succeeds after you've got fired: Go for it. If you are in a r

I would say the same. It is about team size: If you are alone and don't care whether your client succeeds after you've got fired: Go for it. If you are in a really complex structure, you most likely have dedicated database people, who want to do their thing anyway. In any other circumstance, it is a really bad idea to ignore the standards of your framework and build your own thing. If you have to manually change the database, at least stick it into a standard migration. Don't use your own thing. Documentation will be lacking, edge cases will be ignored, the old standard will still stick around and new people will try to use it.