Hi,

Is there a way to override the default behaviour of creating a new record 
where the primary key has been updated?. I would like to update the primary 
key using .store(). I was thinking.... if the original value of the primary 
key was null and then it was changed, then it should insert. If the value 
was not null and it was changed, it should update.

Don't want to get into a primary key update debate, I pretty much never 
update primary keys, but I have a special case :)

Anyway, I don't see an issue with optionally changing the behaviour of 
store()? :)

Thanks, Ryan

Reply via email to