Thanks Dan. Here is a modified script that illustrates the problem I described.
http://gist.github.com/216205 I see the same behavior here as I did with merb. Mark. On Oct 22, 12:20 pm, "Dan Kubb (dkubb)" <dan.k...@gmail.com> wrote: > MarkMT, > > > This appears to be a bug. Unless someone suggests there's something > > obvious I'm missing - which is completely possible, I'll file a ticket > > on lighthouse. > > Since you're running the examples from the merb console, it's > difficult to see which gems you are using -- any of which could be > interacting and causing an issue. The best thing to do in this case > is create a stand-alone script that reproduces the problem in > isolation, eg: > > http://gist.github.com/215552 > > It's best to pair the example down to the minimal amount of "noise", > so only include only the gems you need to reproduce the problem, and > try to make the models as simple as you can. > > -- > > Dan > (dkubb) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to datamapper@googlegroups.com To unsubscribe from this group, send email to datamapper+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---