#567 ✓not-applicable

can't find database adapter when specified as String rather than Symbol

Reported by Nwallins | September 18th, 2008 @ 06:03 PM



adapter: mysql username: luser password: bofh database: test host: localhost

DataMapper.setup(:default, YAML.load_file('database.yaml'))

LoadError: no such file to load -- /var/lib/gems/1.8/gems/dm-core-0.9.5/lib/dm-core/adapters/_adapter

Comments: it should be trying to find mysql_adapter, not _adapter

Workaround: specify the YAML hashkeys as symbols



:adapter: mysql :username: luser :password: bofh :database: test :host: localhost

DataMapper.setup will load correctly

Comments and changes to this ticket

  • Dan Kubb (dkubb)

    Dan Kubb (dkubb) December 2nd, 2008 @ 04:56 AM

    • State changed from “new” to “open”
    • Assigned user cleared.

    Perhaps we should convert the second argument to DataMapper.setup to a Mash when it is a Hash so that the keys can be either String or Symbol objects.

    In fact, a little more broadly, we should think about ensuring that is the case elsewhere in the DM API. Anyplace that accepts a Hash where the keys are Symbols should convert it to a Mash so that the keys may also be String objects.

  • Dan Kubb (dkubb)

    Dan Kubb (dkubb) January 8th, 2009 @ 04:47 AM

    • State changed from “open” to “confirmed”
  • Dan Kubb (dkubb)

    Dan Kubb (dkubb) January 8th, 2009 @ 03:01 PM

    • State changed from “confirmed” to “not-applicable”

    Nwallins: I've thought about this, and I think in the case of DataMapper.setup we'll continue to make it so that it accepts a Hash of Symbol objects. While there are public facing parts of DM that need special consideration for String/Symbol keys, I don't think this is one of them.

    DataMapper.setup is almost never used directly by end users, and when it is we provide a URI based API, and a Hash w/Symbol key API, I wouldn't want to confuse matters by providing a third option. Since there is usually a layer in front of DataMapper.setup, I think it's reasonable to assume that the user-facing layer will perform whatever normalization is necessary on the user supplied data.

    What I'd rather see is merb_datamapper parse the YAML, and then send DataMapper.setup a Mash object. This is preferable to converting to a Mash internally, and should work fine inside DM.

    merb_datamapper is maintained by the merb team, and a ticket can be created here:


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.

New-ticket 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