Oops, sounds like edge.merbivore.com needs updating :-)
Thanks for the heads up
On Oct 14, 2009, at 1:55 PM, Ian Eyberg wrote:
>
> err.. sorry guys..
>
> I've been using edge.merbivore.com to get 1.1 gems
> I should've installed from git from the get go..
>
> Thanks,
> ian
>
> On 13:33 Wed 14 Oct , MarkMT wrote:
>>
>> I also tried to grep some of the code from the second problem Ian
>> referred to and and couldn't find it.
>>
>> I'm using DM 0.10.1 with Merb edge as of four days ago, and haven't
>> found any problems so far.
>>
>>
>> Jacques Crocker wrote:
>>> Hi, I checked merb_datamapper within the latest wycats/merb and it
>>> looks like Martin made the :length change to line 13 of
>>> data_mapper_session.rb about 3 months ago. It might be possible you
>>> are running the wrong merb code. Can you verify?
>>>
>>>
>>>
>>>
>>>
>>> On Oct 14, 2009, at 1:24 PM, Ian Eyberg wrote:
>>>
>>>>
>>>> hrm... I'm using cookie as the session store as well and I'm
>>>> running 1.1 right now
>>>>
>>>> I'll def. send in anything else I find though.
>>>>
>>>> Thanks,
>>>> -ian
>>>>
>>>> On 12:43 Wed 14 Oct , Jacques Crocker wrote:
>>>>>
>>>>> I'm running Merb 1.1 and dm 0.10, however I'm using the Cookie
>>>>> session
>>>>> store, and not datamapper backed sessions. Sounds like things are
>>>>> broken with the data_mapper_session so we should get it fixed.
>>>>> If you
>>>>> find a solution, please post it to the list and hopefully we can
>>>>> get
>>>>> it merged into the upcoming 1.1 release.
>>>>>
>>>>>
>>>>> On Oct 14, 2009, at 12:33 PM, ian wrote:
>>>>>
>>>>>>
>>>>>> 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
-~----------~----~----~----~------~----~------~--~---
