Found a workaround for that weird SQL error:
Without that, Rails would complain: > bind message supplies 5 parameters, but prepared statement "a4" requires 4 However without this workaround it would still work in Rails console, so I still think this is a Rails bug somewhere.
Showing
Please register or sign in to comment