Sean Griffin 2fa746f8f1 Don't magically set up timestamp helpers, create a migration file ... This file is where our initial "plumbing" can go. At the moment we only provide it for PG, and its only behavior is safe to add to existing projects. However, since we're placing this file in other people's projects, and in a structure where once it's run we can't modify it, we should talk about how this file will evolve over time if needed. If we ever do need to add more stuff here, I'd expect this file to just be changed for new projects. For existing projects, I'm thinking we'd provide a `diesel update` command which checks a metadata table with the last version `diesel update` was run against. It will then generate new migrations (versioned normally, we don't want to affect existing tables) to bring everything up to speed. Fixes #522. Close #848.		2017-07-04 10:41:51 -04:00
..
mysql	Allow one form of multi-table joins, generate correct SQL	2017-06-05 12:53:46 -04:00
postgresql	Don't magically set up timestamp helpers, create a migration file	2017-07-04 10:41:51 -04:00
sqlite	Allow one form of multi-table joins, generate correct SQL	2017-06-05 12:53:46 -04:00