Datamapper DataMapper → 0.10.0

Comments and changes to this ticket

• 

  Dan Kubb (dkubb) June 16th, 2009 @ 03:39 AM

  • State changed from “unconfirmed” to “confirmed”
  • Milestone set to “0.10.0”
• 

  Dan Kubb (dkubb) June 23rd, 2009 @ 03:28 AM

  • Assigned user set to “Dan Kubb (dkubb)”
• 

  Dan Kubb (dkubb) June 23rd, 2009 @ 03:29 AM

  • State changed from “confirmed” to “accepted”
• 

  Dan Kubb (dkubb) July 23rd, 2009 @ 11:53 AM

  • Tag set to “regression”
• 

  Dan Kubb (dkubb) August 13th, 2009 @ 11:43 PM

  @Dirkjan: I looked a the spec, and I'm not sure it can be made to pass as-is.

  You're modifying the key in the datastore, and then expecting the current in-memory object to know about the data change. Since we can only reload using the key, when we do reload the object it will not know how to get at the new resource.

  Sure in this specific spec we could wrap it in some sort of block that communicates the changes between two in-memory objects, but I don't think that was your intention.

  Did you mean for a different attribute to be changed, and then reloaded, or something?

• 

  Dirkjan Bussink August 14th, 2009 @ 12:04 AM

  Ah, sorry, my bad. Didn't realize the name attribute was the PK. Yeah, then it should be another attribute that changes and those changes should then be available after a reload.

• 

  Dan Kubb (dkubb) August 14th, 2009 @ 03:11 AM

  • State changed from “accepted” to “resolved”

  (from [93a1091b0cd781c0bf0b2ab2d503b9dc27e93d7b]) Fixed pending spec by modifying a non-key and verifying Resource#reload

  [#898 state:resolved] http://github.com/datamapper/dm-core/commit/93a1091b0cd781c0bf0b2ab...