[DataMapper] Re: Nokogiri redundant for dm-serializer?
nokogiri does not depend on the ruby libxml. -- Yehuda On Sat, Jan 10, 2009 at 5:58 PM, Xavier Shay xavier-l...@rhnh.net wrote: since nokogiri depends on libxml, I suggest that the nokogiri serializer is redundant and can be removed. Thoughts? -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[DataMapper] Multi-Table Inheritence
Hello all! This is my first post to this group, so if this is the wrong place to be asking, I apologize. Anyway, I have a some code at http://gist.github.com/45488 to explain what I'm trying to do, but essentially what I'd like is to have a base model, then have any model that extends it to have its own table. I have looked unsuccessfully for a 'native' feature, so I am reasonably convinced that I will have to build something by hand. My question is, what would be the best way to go about this? Is this a feature that might show up in future? Thanks for your help. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[DataMapper] Re: Multi-Table Inheritence
wrong place to be asking, I apologize. Anyway, I have a some code athttp://gist.github.com/45488to explain what I'm trying to do, but essentially what I'd like is to have a base model, then have any model that extends it to have its own table. I have looked unsuccessfully for a 'native' feature, so I am reasonably convinced that I will have to build something by hand. My question is, what would be the best way to go about this? Is this a feature that might show up in future? What you want to do is really simple using a Module to define the properties and then including that module inside each Model that needs it, like this: http://gist.github.com/45667 I often use this approach to define common properties (like :id, created_at, :updated_at, etc) in a Base module, which I include in all of the Models in my project. 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 -~--~~~~--~~--~--~---
