-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support new CALL command with EVAL-style marshalling (1.7.1+) #101
Comments
After internal discussions we decided that selecting old or new Instead we suggest the following: make call behave in |
LeonidVas
added a commit
that referenced
this issue
Jul 16, 2020
Added support for a new binary protocol command for "call" (used since 1.7.2). The old version of "call" has been moved to "call_16". Closes #101
Merged
LeonidVas
added a commit
that referenced
this issue
Jul 16, 2020
Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). The set_modern_call_mode method was added to switch the "call" to modern mode and back. Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 16, 2020
Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). The set_modern_call_mode method was added to switch the "call" to modern mode and back. Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 17, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). * The use_17_call method was added to switch the "call" to call_17 mode and back. Closes #101
Merged
LeonidVas
added a commit
that referenced
this issue
Jul 21, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_17' => true)); $c->close(); ``` Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 21, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_17' => true)); $c->close(); ``` Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 21, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_17' => true)); $c->close(); ``` Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 21, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_17' => true)); $c->close(); ``` Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 21, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_17' => true)); $c->close(); ``` Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 24, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_17' => true)); $c->close(); ``` Closes #101
LeonidVas
added a commit
that referenced
this issue
Jul 27, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_16' => false)); $c->close(); ``` Closes #101
Totktonada
pushed a commit
that referenced
this issue
Jul 27, 2020
* Added support for a new binary protocol command for "call" (used since tarantool 1.7.2). Unlike the old version, returned data is not converted to tuples (like in case of using "eval"). Default - call_16 mode. * Added options to "call" method. It can be used to force call_16 / call_17 mode. Example: ``` php $c = new Tarantool('localhost', 3301); $c->connect(); $c->call("test_call", array(), array('call_16' => false)); $c->close(); ``` Closes #101
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tarantool 1.7.1 adds a new implementation of CALL command which supports EVAL-style marshalling, i.e. returned data is not converted to tuples anymore. Old CALL command (code = 6) is deprecated.
Please detect Tarantool version on connect and use code=10 for CALL if remote version >= 1.7.1.
tarantool/tarantool#1296
The text was updated successfully, but these errors were encountered: