From: "Timur Safin" <tsafin@tarantool.org> To: 'Chris Sosnin' <k.sosnin@tarantool.org>, v.shpilevoy@tarantool.org Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 4/4] sql: provide a user friendly frontend for accessing session settings Date: Mon, 13 Apr 2020 10:50:52 +0300 [thread overview] Message-ID: <0d6701d61168$41572730$c4057590$@tarantool.org> (raw) In-Reply-To: <20200410154003.23687-1-k.sosnin@tarantool.org> : : I changed it to the following (the main problem with reserved word : persists): : : +///////////////////////////// The SET SESSION command : //////////////////////// : +// : +cmd ::= SET SESSION nm(X) EQ term(Y). { : + sql_setting_set(pParse,&X,Y.pExpr); : +} : + : .. : ========================================================================== : ===== : : Currently if a user wants to change session setting with SQL, one has : to execute UPDATE query like: : [[UPDATE "_session_settings" SET "value" = true WHERE "name" = 'name']] : However, direct access to system spaces isn't considered to be a good : practice. : To avoid that and a bit simplify user's life, we introduce SQL shortcut : command : SET SESSION. : : Closes #4711 : : @TarantoolBot document : Title: API for accessing _session_settings space. : There are two ways of updating values of session settings: : via Lua and SQL. : ... : SQL: : Instead of typing long UPDATE query one can use the SET SESSION command: : `box.execute([[SET SESSION "<setting_name>" = <new_value>]])`. : Note, that this query is case sensitive so the name must be quoted. : Also, SET SESSION doesn't provide any implicit casts, so <new_value> must : be of the type corresponding to the setting being updated. : : Example: : ``` : tarantool> box.execute([[set session "sql_default_engine" = 'memtx']]) : --- : - row_count: 1 : ... : : tarantool> box.execute([[set session "sql_defer_foreign_keys" = true]]) : --- : - row_count: 1 : ... : Like it! (The least intrusive way possible, but still is short for user to write) Timur
next prev parent reply other threads:[~2020-04-13 7:50 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-30 9:13 [Tarantool-patches] [PATCH 0/4] session settings fixes Chris Sosnin 2020-03-30 9:13 ` [Tarantool-patches] [PATCH 1/4] box: replace session_settings modules with a single array Chris Sosnin 2020-04-03 13:32 ` Nikita Pettik 2020-03-30 9:13 ` [Tarantool-patches] [PATCH 2/4] box: add binary search for _session_settings space Chris Sosnin 2020-04-03 14:00 ` Nikita Pettik 2020-04-13 13:40 ` Kirill Yukhin 2020-03-30 9:13 ` [Tarantool-patches] [PATCH 3/4] box: provide a user friendly frontend for accessing session settings Chris Sosnin 2020-04-03 14:47 ` Nikita Pettik 2020-03-30 9:13 ` [Tarantool-patches] [PATCH 4/4] sql: " Chris Sosnin 2020-04-03 15:19 ` Nikita Pettik 2020-04-04 21:56 ` Vladislav Shpilevoy 2020-04-10 15:40 ` Chris Sosnin 2020-04-11 17:18 ` Vladislav Shpilevoy 2020-04-13 7:50 ` Timur Safin [this message] 2020-04-02 9:14 ` [Tarantool-patches] [PATCH 0/4] session settings fixes Timur Safin 2020-04-02 10:18 ` Chris Sosnin 2020-04-03 12:47 ` Nikita Pettik 2020-04-03 13:09 ` Nikita Pettik 2020-04-03 14:02 ` Chris Sosnin 2020-04-13 14:18 ` Kirill Yukhin -- strict thread matches above, loose matches on Subject: below -- 2020-02-17 12:12 [Tarantool-patches] [PATCH 0/4] box: " Chris Sosnin 2020-02-17 12:12 ` [Tarantool-patches] [PATCH 4/4] sql: provide a user friendly frontend for accessing session settings Chris Sosnin 2020-03-16 17:02 ` Nikita Pettik 2020-03-16 22:53 ` Vladislav Shpilevoy 2020-03-17 17:26 ` Chris Sosnin 2020-03-17 20:12 ` Nikita Pettik 2020-03-17 21:00 ` Chris Sosnin 2020-03-18 10:00 ` Chris Sosnin 2020-02-03 22:17 [Tarantool-patches] [PATCH] " Vladislav Shpilevoy 2020-02-04 19:32 ` [Tarantool-patches] [PATCH 4/4] " Chris Sosnin 2020-02-06 22:16 ` Vladislav Shpilevoy 2020-02-07 9:40 ` Chris Sosnin 2020-02-10 22:09 ` Vladislav Shpilevoy 2020-02-17 11:46 ` Chris Sosnin 2020-02-17 11:56 ` Nikita Pettik
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='0d6701d61168$41572730$c4057590$@tarantool.org' \ --to=tsafin@tarantool.org \ --cc=k.sosnin@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 4/4] sql: provide a user friendly frontend for accessing session settings' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox