MySQL 8.4.3
Source Code Documentation
|
Default_object_creation_ctx – default implementation of Object_creation_ctx. More...
#include <table.h>
Public Member Functions | |
const CHARSET_INFO * | get_client_cs () |
const CHARSET_INFO * | get_connection_cl () |
Public Member Functions inherited from Object_creation_ctx | |
Object_creation_ctx * | set_n_backup (THD *thd) |
void | restore_env (THD *thd, Object_creation_ctx *backup_ctx) |
virtual | ~Object_creation_ctx ()=default |
Protected Member Functions | |
Default_object_creation_ctx (THD *thd) | |
Default_object_creation_ctx (const CHARSET_INFO *client_cs, const CHARSET_INFO *connection_cl) | |
Object_creation_ctx * | create_backup_ctx (THD *thd) const override |
void | delete_backup_ctx () override |
void | change_env (THD *thd) const override |
Protected Member Functions inherited from Object_creation_ctx | |
Object_creation_ctx ()=default | |
Protected Attributes | |
const CHARSET_INFO * | m_client_cs |
client_cs stores the value of character_set_client session variable. More... | |
const CHARSET_INFO * | m_connection_cl |
connection_cl stores the value of collation_connection session variable. More... | |
Default_object_creation_ctx – default implementation of Object_creation_ctx.
|
protected |
|
protected |
|
overrideprotectedvirtual |
Implements Object_creation_ctx.
|
overrideprotectedvirtual |
Implements Object_creation_ctx.
Reimplemented in Trigger_creation_ctx.
|
overrideprotectedvirtual |
Implements Object_creation_ctx.
Reimplemented in Trigger_creation_ctx.
|
inline |
|
inline |
|
protected |
client_cs stores the value of character_set_client session variable.
The only character set attribute is used.
Client character set is included into query context, because we save query in the original character set, which is client character set. So, in order to parse the query properly we have to switch client character set on parsing.
|
protected |
connection_cl stores the value of collation_connection session variable.
Both character set and collation attributes are used.
Connection collation is included into query context, because it defines the character set and collation of text literals in internal representation of query (item-objects).