DataMapper sends too much information over the wire
Reported by Jonathan Stott (namelessjon) | July 7th, 2009 @ 07:40 AM | in 0.10.0
DataMapper has recently started sending information which is not required over the wire when persisting a resource to a backend datastore. This only seems to occur on creation of a new resource, but happens irrespective of whether #create or #new is used. The attached script shows this behaviour (see the extra nulls sent for the age property)
Comments and changes to this ticket
-
Dan Kubb (dkubb) July 9th, 2009 @ 01:06 PM
- State changed from “unconfirmed” to “resolved”
(from [0bcbbd7f82663c3ed4386d023317eadaa8eb3c53]) Only persist NULL values for explicitly set columns without defaults
[#958 state:resolved] http://github.com/datamapper/dm-core/commit/0bcbbd7f82663c3ed4386d0...
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 »
People watching this ticket
Dan Kubb (dkubb)
Jonathan Stott (namelessjon)
Attachments
Tags
Referenced by
-
958
DataMapper sends too much information over the wire
[#958 state:resolved]
http://github.com/datamapper/dm-co...