This project is archived and is in readonly mode.
PostgreSQL: use template1 database on rake:db_(create|drop)
Reported by Pete Deffendol | April 22nd, 2008 @ 11:07 PM
Currently the rake:db_create and rake:db_drop tasks will connect to the PostgreSQL server with a nil database, which causes PostgreSQL to look for a database with the same name as the connecting user. This isn't really feasible as the database is not guaranteed to exist.
PostgreSQL always has a template1 database - let's connect to it when creating/dropping other databases.
Comments and changes to this ticket
-
Pete Deffendol April 23rd, 2008 @ 05:33 PM
- no changes were found...
-
Repository April 30th, 2008 @ 11:14 PM
- State changed from “new” to “resolved”
(from [96d9691e71319f4c166315a36b96c2c3c54ed493]) FormHelper#label_tag accepts :for option [encoded] [#38 state:resolved]
-
Pete Deffendol April 30th, 2008 @ 11:50 PM
The previously mentioned commit referenced/closed the wrong ticket. Please reopen.
-
DHH May 1st, 2008 @ 05:25 AM
- State changed from “resolved” to “open”
-
Repository May 4th, 2008 @ 01:21 AM
- State changed from “open” to “resolved”
(from [205750c8dead2449a23173fab0720b7701231d2a]) PostgreSQL: Connect to template1 database when creating or dropping db
- The template1 database is always available on a PostgreSQL install
- The previous behavior expected a database with the same name as the
connecting user, which may not be available
Signed-off-by: Michael Koziarski
[#38 state:resolved]
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
DHH
Repository
Attachments
Referenced by
-
42
PostgreSQL: Use all config options in rake db:create
Yes, but #86 deals with modifying rake db:test:purge to ...