I mirror both of those points, proper dumps to S3 are stopping me putting 2 sites on Heroku at the moment.
Alex On Mar 23, 6:16 am, Chris <[email protected]> wrote: > I just did a heroku db:pull and was VERY bummed to find that all my > foreign key constraints were lost. Luckily I haven't launched the > site yet. Referential data integrity is a major concern, and > obviously my foreign keys are not being implemented on the heroku > database. > > Question: > What is the recommended way for dealing with foreign key constraints > in Heroku if they get lost doing a db:push? > > Side Note: The database interaction is currently the #1 issue why I'm > considering NOT using Heroku. I can deal with the read only > filesystem, but what's the point in using Postgresql if you aren't > going to preserve foreign key constraints? For the little user blog > it probably doesn't matter much, but for any of us that are > considering spending a bunch of money on dynos and dedicated databases > this is a major shortcoming. > > Features that I would consider a must for any realistic business site: > 1) The ability to TRULY dump the database. (pg_dump) Preferably to > S3. And of course the reverse (importing the database). > 2) Access to the database through the console (psql). I realize that > I can access it through the models, this isn't what I want, I want to > be able to login to the console and issue custom sql queries. > > My $0.02 > > So out of curiosity, as a business, who is Heroku's target audience? > > -Chris -- 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.
