Uploaded image for project: 'Mongoid'
  1. Mongoid
  2. MONGOID-2907

`rake db:drop` necessitates re-adding Heroku addon

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.1.3
    • Component/s: None
    • Labels:
      None

      Description

      rake db:drop on a database accessed by URL, either Heroku MongoHQ or Heroku MongoLab, causes the database server to forget the Rails authorized user, at least from a development box. Then through Heroku a new Mongo addon instance and new keys must be generated.

      This problem may be happening on servers other than Heroku, too—I don't know. It doesn't happen on local databases.

      To a new user of Mongo, perhaps this behavior is unexpected. Instead, should this Rake task drop all database documents other than access keys? or reestablish the same keys afterward?

      Heroku's PostgreSQL addon doesn't need this reprovisioning of the Heroku addon after rake db:drop, so I would think therefore the mongoid Rake task shouldn't, either.

      Obviously PostgreSQL drops the database in some different manner, but we should emulate its Rake task's behavior in line with the "philosophy of Mongoid...to provide a familiar API to Ruby developers who have been using Active Record[.]"

      I noticed this happening in version 3.1.2.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            MarkDBlackwell MarkDBlackwell [X] (Inactive)
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: