Not from the exception itself, no. $exception->errorInfo[2] has some useful info, but its contents are engine-specific, so may or may not contain the original SQL query that triggered the error. Why do you want to know the offending SQL query anyway? If you report it back to the user, it could reveal a vulnerability in your code, which could be used by a malicious user as a weak point to break int