I believe you are right db:push and db:pull don't touch FKs; I also agree that FK are a good thing.
If you create a migration file that generates your FKs it will create them when you run rake db:migrate on your heroku application as far as backups go the other option is the single bundle add on I found this gist (i think maybe someone posted it here before?) it downloads the bundle and then uploads it to s3 for back up https://gist.github.com/1d2853b0a349768a8884 (some nice stuff, learned a few things from this code) the only problem with the bundles is all of your code comes with it and most of us probably have that in our own source control system already; I branched that gist above to extract the pgdump.sql file, it needs some additional cleanup; right now the s3 upload is commented out and needs a task to move the pgdump.sql https://gist.github.com/ccfce988fdbc172febc3 The pgdump.sql file from the bundle will contain the FK Alter statements (if the FKs exists on the heroku db) Usually when I use the db:pull; first I'll run rake db:drop and rake db:create -> which will DROP my local development database then run heroku db:pull and then run a script to apply all FKs; getting the pgdump file from the bundle is probably going to be better in most cases. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
