DBRef should not have the default field name "_id" (collision with Models ObjectID)
DBRef should not default to be a key (creates an unwanted cpk)

Fixed and speced this in my pull request.

Hi, can you release an version compatible with dm-migrations (~> 1.2.0) ? Thanks

current rubygems version 0.6.0

HEAD version

gem 'dm-mongo-adapter', git: '[email protected]:solnic/dm-mongo-adapter.git'

I'm having trouble using the mongo adapter now that I have gem installed dm-migrations. This seems to have installed a newer version of dm-core and out of the box this doesn't seem to be compatible.

I managed to make it install by changing the requirements in the Rakefile and changing line 182 of query.rb. It declared a method with the method name on the next line, which seems wrong, but then I'm a ruby noob so I could just not understand some language feature you were using.

BSON rejects hash keys with periods. When you try to BSON-serialize a ruby Hash containing illegal keys, BSON::InvalidKeyName should be raised. When creating a new DataMapper::Mongo::Resource containing such a hash, the error is handled correctly:

class Sample
  include DataMapper::Mongo::Resource
  property :id, ObjectId
  property :data, Hash
end
DataMapper.finalize

invalid_hash = {'bad.key' => 1}
valid_hash = {'good_key' => 1}

Sample.create(:data => invalid_hash)
#=> BSON::InvalidKeyName: bad.key - key must not contain '.'

But if we create a valid resource then later update it with an invalid hash, the failure is silently dropped.
The resource appears to have been persisted, even though Mongo never accepted the data:

a = Sample.create(:data => valid_hash)
#=> #<Sample @id=BSON::ObjectId('4fce0d32faa3171f99000004') @data={"good_key"=>1}>

a.update(:data => invalid_hash)
#=> true

a.data
#=> {"bad.key"=>1}

a.persisted?
#=> true

a.dirty?
#=> false

b = Sample.first
#=> #<Sample @id=BSON::ObjectId('4fce0d32faa3171f99000004') @data={:good_key=>1}>

a == b
=> true

Hello,

I created a fresh rails 3.0 app with dm-rails and I am trying to use mongo-adapter. Here is what I get:

/Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-core-1.0.0/lib/dm-core.rb:327:in finalize_model': DataMapper::Mongo::EmbeddedResource must have at least one property or many to one relationship to be valid (DataMapper::IncompleteModelError) from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-core-1.0.0/lib/dm-core.rb:309:infinalize'
from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-core-1.0.0/lib/dm-core/model/descendant_set.rb:33:in each' from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-core-1.0.0/lib/dm-core/model/descendant_set.rb:33:ineach'
from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-core-1.0.0/lib/dm-core.rb:308:in finalize' from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-rails-1.0.0/lib/dm-rails/setup.rb:43:infinalize'
from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-rails-1.0.0/lib/dm-rails/setup.rb:50:in preload_models' from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/dm-rails-1.0.0/lib/dm-rails/railtie.rb:83:in_callback_before_7'
from /Users/juggy/.rvm/gems/ruby-1.8.7-p174/gems/activesupport-3.0.0.beta4/lib/active_support/callbacks.rb:423:in `_run_prepare_callbacks'

I have a single Mongo::Resource defined, no EmbeddedResource. When I do create an EmbeddedResource, it then seems to work.

I use the git master as the gem to run this.

Thanks,
Julien.

There is a convention about a "DBRef" in mongo. dm-mongo-adapter does not follow this convention so the property should not be named after it.

Suggestion:

Rename DBRef it to ObjectId, and rename ObjectId to some better name g.

I read the irclogger, there was a discussion about a "universal general record identifiing cross datastore property" month ago. Maybe this issue is related to this discussion.

Defining a property of type Hash or Array in an embedded document causes the following error: "[...] property.rb: `initialize': +type+ was Hash, which is not a supported type (ArgumentError)".

And it would be nice to chain embedded documents, but the method "embeds" is not defined for an EmbeddedResource.

Thank you, this really rocks (-;

This gem is dependent on the 'extlib' gem. When it is not in your Gemfile (using bundler) this adapter will fail on several places.

Hello,

How can I execute mongo's db.auth with your adapter?

I think it shouldn't be necessary but for some reasons I keep getting:
cursor.rb:86:in `next_document': unauthorized db:db_name lock type:-1 client:127.0.0.1 (Mongo::OperationFailure)

Thanks!

NoMethodError: undefined method `timestamps' for Book:Class

Adding dm-timestamps 10.2... it doesnt seem to recognize the timestamps :at command on my models