status?

[linoj]

Hiya,

I've been playing with Rails3beta with mongomapper and mongoid the
past week, and started wondering why are they reinventing the wheel?
Then i discovered http://github.com/solnic/dm-mongo-adapter/ and this
group (?!). A DM adapter seems a more intuitive direct approach.
What's the status of this project? it seems the other wrappers
presently have more momentum, but is that the right approach?

[lancecarlson]

Yes this is the group. I actually believe this adapter is pretty far
along. It lacks some of the embedded document features but this is
currently getting worked on. I would venture to say that this adapter
is actually further along than the active record integration that was
worked on by the 10gen guys (mainly because they have said they're no
longer maintaining that project right now.. at least for the moment).

On Feb 22, 1:02 pm, linoj <lino...@gmail.com> wrote:
> Hiya,
>
> I've been playing with Rails3beta with mongomapper and mongoid the
> past week, and started wondering why are they reinventing the wheel?

> Then i discoveredhttp://github.com/solnic/dm-mongo-adapter/and this

[solnic]

On Feb 22, 7:02 pm, linoj <lino...@gmail.com> wrote:
> Hiya,
>
> I've been playing with Rails3beta with mongomapper and mongoid the
> past week, and started wondering why are they reinventing the wheel?

Probably because they are not familiar with DataMapper.

> Then i discoveredhttp://github.com/solnic/dm-mongo-adapter/and this

> group (?!). A DM adapter seems a more intuitive direct approach.

Yes it is, however it's not as easy as you might think :)

> What's the status of this project?

There's a pre-release available as a gem. I'm using it in 2
applications
but in a very basic setups, no issues so far.

The first stable and fully-featured release will be done along with
the
DataMapper 1.0 release which should happen during next...few months.
I'm
working on various major improvements in dm-core at the moment that's
why I
haven't done much work in the adapter lately. Most of the upcoming
changes in
dm-core will make possible to implement mongo-specific features
without
altering DataMapper's private API, like embedded documents or handling
of
custom property types like Array and Hash.

> it seems the other wrappers presently have more momentum, but is that the
right approach?

With DataMapper you get a lot for free so you don't have to implement
everything from scratch AND you get a bunch of various extensions and
plugins.
For instance I didn't have to implement timestamps, pagination,
aggregations
etc. I just used available DataMapper plugins. That's a great
advantage over
writing a dedicated Mongo framework like MM or Mongoid. We just need
to
finalize DataMapper itself and then the development of the adapter
will be much easier.

Cheers!

solnic

[gboersma]

DataMapper plus MongoDB? Lots of goodness! I am keen on this one (e.g.
http://lunarlogicpolska.com/blog/2010/02/15/mysql-and-mongodb-working-together-in-kanbanery.html
sounds yummy).

I would like to contribute, but I need to spend some time learning the
basics. Do you mind some newbie questions? (Google didn't help me much
on these).

- Dependencies include 'dm-core', '~> 0.10.3'. Current gem is 10.2. I
assume that this means dm-core must be built from git master?
- Dependencies include 'mongo', '= 0.19.3'. Why is version 19.3
required? Seems a bit behind.
- Dependencies include 'mongo_ext', '= 0.19.3'. I am using JRuby and
mongo_ext does not apply. Is this dependency really required? (I know,
I know- there is talk of getting a similar Java-enabled gem in place;
just waiting until it happens).
- Dumb question: What does '~>' in a dependency version mean?

Thanks,
Gerald



--
Subscription settings: http://groups.google.com/group/dm-mongo-adapter/subscribe?hl=en

[solnic]

On Apr 15, 7:11 am, gboersma <gerald.boer...@gmail.com> wrote:
> DataMapper plus MongoDB? Lots of goodness! I am keen on this one (e.g.http://lunarlogicpolska.com/blog/2010/02/15/mysql-and-mongodb-working...
> sounds yummy).

Yeah that setup works really nicely for us :)

> I would like to contribute, but I need to spend some time learning the
> basics. Do you mind some newbie questions? (Google didn't help me much
> on these).

I'm not surprised things are changing so rapidly that even Google
can't catch up ;)

> - Dependencies include 'dm-core', '~> 0.10.3'. Current gem is 10.2. I
> assume that this means dm-core must be built from git master?

Yeah, exactly. Take a look at the Gemfile it includes all the
development deps. Development of the adapter goes inline with dm-core
right now. I've been spending more time on dm-core lately because we
need to do various improvements there before pushing the adapter
forward.

> - Dependencies include 'mongo', '= 0.19.3'. Why is version 19.3
> required? Seems a bit behind.

I did an upgrade yesterday to 0.20 :)

> - Dependencies include 'mongo_ext', '= 0.19.3'. I am using JRuby and
> mongo_ext does not apply. Is this dependency really required? (I know,
> I know- there is talk of getting a similar Java-enabled gem in place;
> just waiting until it happens).

Good point! No, it's not required, it's just highly recommended for
obvious reasons. I'll remove it anyway.

> - Dumb question: What does '~>' in a dependency version mean?

"> 1.2.0" - this accepts anything above 1.2.0
"~> 1.2.0" - this accepts all 1.2.x upgrades, so ie 1.3.0 won't be
installed

I'm gonna update TODO file soon so if you want you can start working
on something from the list - just fork and have fun :)

Cheers!

solnic

[Gerald Boersma]

Thanks, that helps. I am getting and building the latest.

Some more dependency questions (based on latest in master):

- Is Rails 3 active support really required? I don't want to be forced to Rails 3 quite yet.
- is bson_ext really required? Seems like this is the new mongo_ext replacement for 0.20.0 of the mongo driver. Won't work for JRuby.

Thanks,
Gerald

[solnic]

On Apr 16, 5:44 pm, Gerald Boersma <gerald.boer...@gmail.com> wrote:
> Thanks, that helps. I am getting and building the latest.
>
> Some more dependency questions (based on latest in master):
>
> - Is Rails 3 active support really required? I don't want to be forced to Rails 3 quite yet.

Yes, edge adapter requires ActiveSupport, it's preferred over Extlib.
Sooner or later DM will drop support for Extlib anyway.

> - is bson_ext really required? Seems like this is the new mongo_ext replacement for 0.20.0 of the mongo driver. Won't work for JRuby.

That will go away :)