#584 dm-aggregates return nil value when working with enums - DataMapper

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#584 ✓resolved

dm-aggregates return nil value when working with enums

Reported by coryodaniel | October 4th, 2008 @ 03:57 PM | in 1.0.0

I was doing some conditional aggregating based on an enum field.

MyObject.all(:somefield => :great).aggregate(:somefield.count, :somefield, :other_field, :etc)

The result set comes back: [[32,nil,1,2],[322,nil,23,1]]

I know what the field is because I specified it in the #all method, but when it maps back the enum value in the results, it displays nil.

Comments and changes to this ticket

Dan Kubb (dkubb) January 8th, 2009 @ 05:07 AM
- State changed from “new” to “accepted”
- Assigned user changed from “Sam Smoot” to “Dan Kubb (dkubb)”
Dan Kubb (dkubb) June 7th, 2009 @ 04:01 AM
- State changed from “accepted” to “unconfirmed”
- Assigned user changed from “Dan Kubb (dkubb)” to “Michael Klishin (antares)”
Jonathan Stott (namelessjon) August 28th, 2009 @ 12:19 PM
- Tag changed from “aggregates, bug” to “0.10.0, aggregates, bug”
- State changed from “unconfirmed” to “confirmed”
Confirmed. Attached is a standalone script which demonstrates the issue.
- 584-dm-aggregates-return-nil-value-when-working-with-enums.rb 704 Bytes
Dan Kubb (dkubb) February 4th, 2010 @ 05:00 AM
- State changed from “confirmed” to “resolved”
(from [19b171069e85630498031c59df3f81b66cff6fb0]) [dm-aggregates] Use Property#load to load the values from the datastore
- This change allows a normal and custom property to be used interchangeably
- Previously used Property#typecast, which is primarily geared towards taking external input and converting it into an internal representation.
[#584 state:resolved] http://github.com/datamapper/dm-more/commit/19b171069e85630498031c5...
Dan Kubb (dkubb) February 4th, 2010 @ 05:00 AM
(from [19b171069e85630498031c59df3f81b66cff6fb0]) [dm-aggregates] Use Property#load to load the values from the datastore
- This change allows a normal and custom property to be used interchangeably
- Previously used Property#typecast, which is primarily geared towards taking external input and converting it into an internal representation.
[#584 state:resolved] http://github.com/datamapper/dm-more/commit/19b171069e85630498031c5...
Dan Kubb (dkubb) February 4th, 2010 @ 05:01 AM
- Assigned user changed from “Michael Klishin (antares)” to “Dan Kubb (dkubb)”
- Milestone set to “1.0.0”
This is fixed in edge dm-more. Marking this as resolved because github is down (again), and the post-commit message probably won't fire -- if it does, then this will link to the commit that fixes the problem.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins (Sort)

People watching this ticket

Attachments

584-dm-aggregates-return-ni... 704 Bytes

Referenced by

584 dm-aggregates return nil value when working with enums [#584 state:resolved] http://github.com/datamapper/dm-mo...
584 dm-aggregates return nil value when working with enums [#584 state:resolved] http://github.com/datamapper/dm-mo...
1191 custom dm-types don't properly deserialize when aggregated This was resolved in the fix #584 to dm-more yesterday:

Datamapper DataMapper → 1.0.0