No strategy for updating resource keys
Reported by Carl Porth | July 2nd, 2008 @ 07:50 PM
Currently there is no strategy for updating a resource's key. Either you should not be allowed to do so (with an error being raised) or you should.
Right now the query passed to Adapter#update(attributes, query) contains dirty attributes (including key attributes). This is problematic because the adapter cannot use the key in the query to find the resource if it has changed.
In order to solve this, the original attributes of the key would have to be passed to the query so that the resource can be found and updated.
I have attached a simple example which illustrates the problem. Note the UPDATE log statement which uses the dirty id to update the resource.
Comments and changes to this ticket
-
Jonathan Stott (namelessjon) November 30th, 2008 @ 08:17 AM
- State changed from “new” to “resolved”
- Assigned user cleared.
Resolved in 0.9.7
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
- Nobody is watching this ticket.