There was a similar problem: I needed to regenerate a large table with data, and I safely put everything in the transaction. When I tried to run the code, 405 also crashed. The solution is to see the debugger (if any). In my case, I used an incorrect ActiveRecord class that referred to a completely different table.
Update: the error is implicit, and in the case of working with transactions, it can crash to any school for which the transaction failed.
My advice: run your code out of the transaction first, if everything is good, then enter it inside. It may seem trivial, but I'm with almost the same code in 1 of 3 methods on a data pool so well, just ****
POSTmethod, and you request usingGET.POST- a request to simply form using the forms that you most likely is happening, and the button you apparentlysubmit. A simple way to generate a POST request using the address bar will not work. - Denis Bubnov