Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

rails dbconsole doesn't work for DM/Sequel + PostgreSQL

#6180

Because the dbconsole command only accepts 'postgresql' for the driver name while these ORMs are using 'postgres'.

This is a patch for making them work.

Reported by Akira Matsuda · December 16th, 2010 @ 01:20 PM

State: committed
Milestone: none
Assigned to: nobody
Importance: Low

Activity

  1. Santiago Pastorino
    Santiago Pastorino
    • Importance changed from to Low

    Hey Akira can you add a test case?

    January 31st, 2011 @ 09:54 PM

  2. Akira Matsuda
    Akira Matsuda

    Yes, I'm willing to. But, are there any existing test case for dbconsole command? I couldn't find the file.

    January 31st, 2011 @ 10:03 PM

  3. Santiago Pastorino
    Santiago Pastorino

    I'm pushing it, since we don't have tests for that :(.
    Akira thanks for your work but please provide the [#OMG state ... comments for autoclosing the tickets in your next contributions :).

    Thanks you.

    February 1st, 2011 @ 03:22 PM

  4. Repository
    Repository
    • State changed from new to committed

    (from [8a85f64abffde29ddfd521d63d566f98796ae400]) Accept 'postgres' as a PostgreSQL driver name in dbconsole for non-AR ORMs like DataMapper and Sequel

    [#6180 rails dbconsole doesn't work for DM/Sequel + PostgreSQL state:committed]

    Signed-off-by: Santiago Pastorino santiago@wyeworks.com
    https://github.com/rails/rails/commit/8a85f64abffde29ddfd521d63d566...

    February 1st, 2011 @ 03:23 PM