Table.update has problems with UUID keys
Created by: dmfay
This one's got a couple parts, and fair warning I may be a little off on the details; I'm writing this up the day after I found everything to accompany another pull request :)
- If you're trying to save an object with a UUID primary key, it sets up the WHERE clause as 'WHERE id = $1' regardless of how many other parameters exist, and then the parameter list is one short because Table.save only expects integer pkeys and deletes the key.
- As mentioned above, it deletes the ID -- from the original object. I realize referencing the old object is kind of a kludgey use case anyway but it's untidy.