This project is archived and is in readonly mode.
rails dbconsole doesn't work for DM/Sequel + PostgreSQL
Reported by Akira Matsuda | December 16th, 2010 @ 01:20 PM
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.
Comments and changes to this ticket
-
Santiago Pastorino January 31st, 2011 @ 09:54 PM
- Importance changed from “” to “Low”
Hey Akira can you add a test case?
-
Akira Matsuda January 31st, 2011 @ 10:03 PM
Yes, I'm willing to. But, are there any existing test case for dbconsole command? I couldn't find the file.
-
Santiago Pastorino February 1st, 2011 @ 03:22 PM
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.
-
Repository February 1st, 2011 @ 03:23 PM
- 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 state:committed]
Signed-off-by: Santiago Pastorino santiago@wyeworks.com
https://github.com/rails/rails/commit/8a85f64abffde29ddfd521d63d566...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Akira Matsuda
Jeremy Kemper
Piotr Sarnacki
Santiago Pastorino
Attachments
Referenced by
-
6180
rails dbconsole doesn't work for DM/Sequel + PostgreSQL
[#6180 state:committed]