Avoid call_user_func_array in query method

If we take this route, we should remove any trace of overloading and request that end users use executeQuery when they want to use that method and query when they want to use the other method.



--
Korvin Szanto

On November 5, 2014 at 9:35:27 AM, Joe Meyer (notifications@github.com) wrote:

2 - Allow for ONLY arrays as the second parameter to be bound, and if they pass a second parameter that's not an array we toss it to the normal query function, and if they don't pass the correct type, they will likely get an error at a deeper level (since PDO::query expects parameter 2 to be an integer). The downside to this of course is that if people were relying on that string value binding, we just broke their stuff (of course it's currently broken and we haven't heard any complaints about it I'm aware of so now would be the time to make the change).