DataMapper

Comments and changes to this ticket

• 

  Dan Kubb April 19th, 2008 @ 03:04 AM

  • → State changed from “new” to “open”
  • → Milestone changed from “” to “0.9.0”

  I would implement this using the standard property() method, and have it accept an argument like :persistable => true|false, or maybe :virtual => true|false.

• 

  Sam Smoot April 27th, 2008 @ 10:34 PM

  :virtual => true|false. I like it...

• 

  Adam French May 7th, 2008 @ 09:02 PM

  can we use DataMapper::Validate on attr_accessors, rather than full properties?

  class Thing
    include DataMapper::Resource
    include DataMapper::Validate
  
     # properties here
     attr_accessor :woo
  
     validates_presence_of :woo
     validates_format_of :woo, :with => /^([^@\s]+)@((?:[-a-z0-9]+\.)+[a-z]{2,})/i
  end
  

  if so, then we don't really need :virtual

• 

  Nathan Herald May 8th, 2008 @ 07:54 AM

  I think an advantage of doing it through the property method is that you can have default and dirtiness. Although dirtiness may get in the way during saving, so I am not sure on that one.

• 

  Sam Smoot May 8th, 2008 @ 02:39 PM

  • → State changed from “open” to “invalid”

  Ah yes. Having them go into dirty attributes would screw things up. And since you can already validate arbitrary accessors, the only use-case for this is :default. Which you can also handle by overwriting #initialize.

  I think for now it might not be as compelling an idea as I thought. I'm going to close this for now and see if it comes back up in the future...