it appears there are several things that merb_datamapper 1.1 does not
like about dm 0.10
the first fix was rather easy:
line 10 on /usr/lib/ruby/gems/1.8/gems/merb_datamapper-1.1/lib/merb/
session/data_mapper_session.rb
says this:
property :session_id, String, :size => 32, :nullable =>
false, :key => true
it should read this:
property :session_id, String, :length => 32, :nullable =>
false, :key => true
however I was still stuck on this one just cause I don't really know
dm's internals:
line 59-65 are erroring out as well:
descendants = DataMapper::Resource.descendants.dup
descendants.dup.each do |model|
descendants.merge(model.descendants) if model.respond_to?
(:descendants)
end
descendants.each do |model|
model.relationships.each_value { |r| r.child_key }
end
tried replacing 'Resource' with 'Model' but merge isn't going to
respond to the descedents...
anways... anyone have patches/walkthroughs for getting dm0.10.x and
merb-edge running together??
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
