Constants§

  • This value means focus on readability, not on ability to parse back, etc.
  • This is used for EXPLAIN EXTENDED extra warnings / Be more detailed Be more detailed than QT_EXPLAIN. Perhaps we should eventually include QT_ITEM_IDENT_SKIP_CURRENT_DATABASE here, as it would give better readable results
  • Print for FRM file. Focus on parse-back. e.g. VIEW expressions and virtual column expressions
  • If Item_cache_wrapper should not print <expr_cache>
  • Do not print database name or table name in the identifiers (even if this means the printout will be ambigous). It is assumed that the caller passing this flag knows what they are doing.
  • If identifiers should not include database names, where unambiguous
  • If identifiers should not include table names, where unambiguous
  • If NULLIF(a,b) should print itself as CASE WHEN a_for_comparison=b THEN NULL ELSE a_for_return_value END when “a” was replaced to two different items (e.g. by equal fields propagation in optimize_cond()) or always as NULLIF(a, b). The default behaviour is to use CASE syntax when a_for_return_value is not the same as a_for_comparison. SHOW CREATE {VIEW|PROCEDURE|FUNCTION} and other cases where the original representation is required, should set this flag.
  • If Item_subselect should print as just “(subquery#1)” rather than display the subquery body
  • good for parsing
  • This is used for EXPLAIN EXTENDED extra warnings / Be more detailed Be more detailed than QT_EXPLAIN. Perhaps we should eventually include QT_ITEM_IDENT_SKIP_CURRENT_DATABASE here, as it would give better readable results
  • Nothing specific, ordinary SQL query.
  • good for parsing
  • Print for FRM file. Focus on parse-back. e.g. VIEW expressions and virtual column expressions
  • This value means focus on readability, not on ability to parse back, etc.
  • In utf8.
  • view internal representation (like QT_ORDINARY except ORDER BY clause)
  • Without character set introducers.

Type Aliases§

  • Query type constants (usable as bitmap flags).