#455 Saving a relation doesn't always properly set the foreign key in case of new objects - 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:id	tickets sorted by id (creation time)
Combine keywords for powerful searching.
Use advanced searching »

#455 √ resolved

Saving a relation doesn't always properly set the foreign key in case of new objects

Reported by Dirkjan Bussink | July 14th, 2008 @ 11:19 AM

I've whipped up a spec here:

Dirkjan Bussink July 14th, 2008 @ 11:21 AM
- → Tag changed from “” to “associations belongs_to bug dm-core”
- → Assigned user cleared.
Bernerd Schaefer July 30th, 2008 @ 11:05 AM
- → State changed from “new” to “resolved”
This is resolved in f714e0b. Thanks for the failing spec.

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

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