This project is archived and is in readonly mode.
PostgreSQL: update rake tasks to use full settings from database.yml - bugfix
Reported by eagleas | May 12th, 2008 @ 09:30 AM
After http://github.com/rails/rails/co... commit in db:test:purge, drop_database on configuration with schema_search_path broken:
rake aborted!
PGError: ERROR: schema “my_schema” does not exist
: SET search_path TO my_schema
When we connect to 'template1' database only for delete *_test database, we do not have there "my_schema".
In patch we do not apply schema if database is default 'template1'.
Comments and changes to this ticket
-
Repository May 13th, 2008 @ 06:26 PM
- State changed from “new” to “resolved”
(from [3fee2378edd45188e41a7d14d4ca0a88280b541e]) Use 'public' schema path when connecting to 'postgres' database. [#170 state:resolved]
Signed-off-by: Pratik Naik
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>
eagleas
Michael Koziarski
Repository