FreeTDS doesn't seem to be returning the general error number any more, ... #446
Conversation
…e, but the actual error number. This means that you get no useful error messages whatsoever. This change shows the message handler's string instead of the error string, whenever the severity > 0
|
Please note that this change has effectively already been made in unreleased FreeTDS source code: http://gitorious.org/freetds/freetds/commit/bc22b2ef817fb5d102bd758111ff3634b39a1319 Note how the msgno is no longer relevant, it is hard-coded to the special message no. Once this FreeTDS version is released, PHP will be fixed, however we can put my pull request in in the meantime to solve the problem for all users of all versions of FreeTDS. |
|
/cc @adambaratz Is this PR still relevant? |
|
Thanks for calling this out. It might be. I actually did a similar patch for my employer. It was on my todo list to see whether it should be cleaned up for broader use. This patch might be the cleaned up version, so I'll do some more testing and merge if needed. |
|
I haven't tried this with updated PHP or FreeTDS for a while, so no idea if it's still needed sorry. Not having error messages really, really hurts though. |
|
The fix in question was from 2013. Hopefully people aren't running versions of FreeTDS that are so old. That said, there's no harm in including this change. |
|
Comment on behalf of adambaratz at php.net: Merged into PHP-7.0 and up. |
This fixes the problem that error messages are no longer returned in pdo_dblib. It's because dberr is never set to SYBESMSG anymore?