… no results
…ssing/working with them a bit easier. Will probably try to do something a bit more sophisticated eventually, but seems a step in the right direction
… I think this is a better fit for what we want in the type field (since it will be per record and not per table)
…be more consistent with other parts of datamapper AND respect table_name options
… to use better namespacing for VERSION, and to use gem "dm-core" linked to their own VERSION.
This stops applications which require 'dm-types' from breaking automatically on applying this update, by attempting to require the bcrypt gem. specs are tweaked to only run if the file can be loaded too, otherwise they are pending.
This currently doesn't work, and I am not sure why.
BCrypt is the password scheme used OpenBSD and features a variable cost. This integrates BCryptHashes into DataMapper. plain text passwords are transparently converted to BCryptHashes for database storage and converted back out to BCrypt Passwords on retrival.
…tead of just a single create
…the only condition is key == blah), should be much faster and more effecient than building an ad hoc view
dm-timestamps, dm-types, dm-validations, merb_datamapper
…atile than the hard coded object dump
…mething like an IN, ie x == a || x == b || x == c, etc. Needed for deeper relationships, like city.first.zoo.first.animals