dm-constraints should not create classes for unavailable database adapters
Reported by Dan Walters | October 23rd, 2008 @ 08:36 PM
The dm-constraints init script (re)opens the DataMapper::Adapters::PostgresAdapter class, regardless of whether the postgres adapter is installed. Other gems (dm-types's UUID, for example) check for whether adapter class is defined to determine whether that adapter is loaded.
The current situation is such that if you don't have postgresql installed and require dm-constraints before dm-types, you'll get an error due to the lack of postgres support.
If you require dm-constraints after dm-types, everything is fine, but things obviously shouldn't be quite that sensitive.
Comments and changes to this ticket
-
Dan Kubb (dkubb) December 5th, 2008 @ 05:00 AM
- Tag changed from “adapter, bug, constraints, dm-constraints, dm-types, postgres, types” to “bug, dm-constraints, dm-more”
- State changed from “new” to “resolved”
- Assigned user cleared.
This should be resolved by the following commit:
http://github.com/sam/dm-more/co...
Please reply if it is not resolved for you and I will re-open this ticket.
Marking as resolved.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
People watching this ticket
- Nobody is watching this ticket.