I agree, it should be something very simple. I ended up trying the database approach in my latest project, but then I started thinking about schema/migrations. I totally missed out the file option that you and @superkuh suggested. It's either that or the Google Forms hack that @stocknoob pointed out, which I'm hoping could be used for ajax requests too.
back
1 comments
Why would you need a migration for this?
In case I change the schema for whatever reason.
But why?
This data doesn’t need to persist forever. You could literally drop the table (after doing a backup) anytime you need to make a migration.
I agree the data doesn't need to persist forever, but I don't want to think about backups either. Fussy, I know :)