This project is archived and is in readonly mode.
Postgresql adapter breaks tests with Postgresql 8.3
With Postgresql 8.3 and TSearch2 some of the TSearch2 specific tables (pg_ts_dict, pg_ts_parser) are not just present in the public schema within which the application database exists, but also in the pg_catalog schema.
As they're consequently system tables, when running tests and using SQL format for generation of the test database structure the postgresql connection adapter attempts to enable or disable triggers on the TSearch2 tables, which raises a permissions issue. You have to use SQL format for creating the test database as the TSearch2 tables have no corresponding model and are not exported in the ruby schema normally used.
This wasn't an issue with PostgreSQL 8.1, as the TSearch2 tables were only in the public schema, and not system tables.
A solution is to exclude any tables in the exported SQL dump which are also in the pg_catalog schema.
Difficult to provide a self-contained test for this, since it requires testing against a Postgresql 8.1 and 8.3 db.
-
postgresql_8.3_fix.diff
1.43 KB
-
Jeremy Kemper- Milestone changed from 2.x to 3.x
- Tag changed from active_record, connection, postgres, postgresql to active_record, connection, patch, postgres, postgresql
-
laiji- Importance changed from to
ion models tiffany the vision, values, objectives Pandora jewelry again aims of the Bvlgari Ring replica company. indubitable stipulates the tiffanys capital objectives again accomplishment Juicy Couture jewelry replica prospects that guide board replica Juicy Couture jewelry further inside track decisions. Gucci jewelry Owners further warrant an Tiffany 1837 overall idea of the Tiffany Necklaces replica camper that ofttimes defines replica Links of London jewelry the burden design. This spells
-
Andrea CampiIs this still an issue with newer Rails and newer Postgres?
-
Santiago Pastorino
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino
- State changed from open to stale