Datamapper DataMapper → 1.0.0

Comments and changes to this ticket

• 

  Lindsay Holmwood June 16th, 2009 @ 04:02 PM

  • State changed from “unconfirmed” to “confirmed”

  I can confirm this behaviour.

• 

  Martin Gamsjaeger (snusnu) July 9th, 2009 @ 02:29 PM

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

  I assigned that ticket to Dan, mainly because I wanted it to pop up prominently on the first page in LH again and I'd love to see it resolved. Maybe I can try to look into it myself in the next few days, but hopefully it will be low hangin' fruit for Dan :)

• 

  Dan Kubb (dkubb) July 22nd, 2009 @ 03:57 PM

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

  Dan Kubb (dkubb) October 4th, 2009 @ 09:33 PM

  • Milestone changed from “0.10.0” to “0.10.2”

  [project:id#20609 not-tagged:"0.10.0" milestone:id#51895 bulk edit command]

• You flagged this item as spam.
  

  Kai Chen October 11th, 2009 @ 11:45 AM

  I wrote a patch to fix this problem:
  http://github.com/kaichen/dm-core/commit/5117be5ebcc261225b0aae8c9c...

  Here is a test script: http://gist.github.com/207748

• 

  Dan Kubb (dkubb) February 1st, 2010 @ 04:33 PM

  • Milestone changed from “0.10.2” to “1.0.0”

  [bulk edit]

• 

  Dan Kubb (dkubb) February 2nd, 2010 @ 02:34 AM

  • Assigned user cleared.

  [bulk edit]

• 

  Dan Kubb (dkubb) February 2nd, 2010 @ 02:45 AM

  • Milestone cleared.

  [bulk edit]

• 

  Dan Kubb (dkubb) February 2nd, 2010 @ 02:47 AM

  • State changed from “accepted” to “confirmed”

  [bulk edit]

• 

  Dan Kubb (dkubb) February 4th, 2010 @ 03:51 AM

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

  Dan Kubb (dkubb) February 4th, 2010 @ 03:52 AM

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

  Dan Kubb (dkubb) February 4th, 2010 @ 03:52 AM

  • State changed from “accepted” to “resolved”

  (from [c65fd07674205afc9d9d78670b738ffa2ee9572b]) Fixed paranoid types

  • Fixed hooks to work with Resource#destroy when paranoid type used
  • Specified behaviour of Resource#destroy and Resource#destroy! when a paranoid type is used
  • Specified behaviour of Model#with_deleted when a paranoia property is declared. Previous behaviour seemed broken, since it would only have returned deleted resources, but "with deleted" implies you will be returning all resources, including the deleted ones.
  • Moved common code from paranoid types into a module

  [#520 state:resolved] [#883 state:resolved] http://github.com/datamapper/dm-core/commit/c65fd07674205afc9d9d786...