Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | MDEV-13384 - misc Windows warnings fixed | Vladislav Vaintroub | 2017-09-28 | 1 | -2/+2 |
| | |||||
* | Correct FSF address | iangilfillan | 2017-03-10 | 1 | -1/+1 |
| | |||||
* | MDEV-3802: Millisecond timeout support in non-blocking client library + fix ↵ | unknown | 2012-10-12 | 1 | -5/+5 |
| | | | | | | | | | | | | | | | | | | | incorrect blocking. After the merge of VIO stuff from MySQL 5.6, there were some bugs left in the non-blocking client library: - vio_io_wait() was introduced without any support for non-blocking operation, so async queries could turn into sync. - Timeouts were changed to milliseconds, but this was not reflected in the non-blocking API, also semantics was changed so signed -1 was used for "no timeout" rather than unsigned 0. Fix by implementing and using my_io_wait_async() in the non-blocking case. And by introducing a new mysql_get_timeout_value_ms() API function that provides the timeout with millisecond granularity. The old mysql_get_timeout_value() is kept and fixed to work correctly, converting the timeout to whole seconds. | ||||
* | Fix non-ssl build. | unknown | 2012-01-08 | 1 | -0/+2 |
| | |||||
* | MWL#192: non-blocking client API, after-review fixes. | unknown | 2012-01-06 | 1 | -0/+36 |
Main change is that non-blocking operation is now an option that must be explicitly enabled with mysql_option(mysql, MYSQL_OPT_NONBLOCK, ...) before any non-blocing operation can be used. Also the CLIENT_REMEMBER_OPTIONS flag is now always enabled and thus effectively ignored (it was not really useful anyway, and this simplifies things when non-blocking mysql_real_connect() fails). |