Woody Gilk
Woody Gilk
Or you can replace this PR with one that updates the docs. Your choice.
Latitude doesn't have any helpers to specifically deal with `case ... end`, but it is possible to do this with expressions.
This was actually an intentional decision, because I couldn't think of a single use case for having an update statement with `LIMIT`. Do you have a real world example?
Does that actually change performance? I assume that `id` is a primary key, so I don't think anything would be gained by doing that. Have you run `EXPLAIN` on it...
The standard SQL way to do this is with a sub-select: ```sql UPDATE users SET trending = 1 WHERE id IN ( SELECT id FROM users ORDER BY likes DESC...
I'd be happy to take a PR to add `LIMIT`, etc to MySQL update/delete queries. It just holds no interest for me because I don't use MySQL and I don't...
For deletes best practice is to always use a limit to prevent coding errors from deleting the entire table.
Using kernel 2.6.31 works. Now I have a separate issue with using Ruby 1.9.1, but will investigate that separately. Thanks!
@kelunik I'll rename the PR.
Yes, I've confirmed that `sink` works correctly when this middleware is disabled. Guzzle [config is here](https://github.com/RoundingWellOS/redox-php/blob/feature/json-schema/config/injection/guzzle.php#L22) and here is our [calling code](https://github.com/RoundingWellOS/redox-php/blob/feature/json-schema/bin/download#L35-L36), which is currently not using `sink` due to...