mariadb

Tree: 985d2d393c

Author	SHA1	Message	Date
Marko Mäkelä	40bf5c951b	Fix a Bison warning about semantic type clash in default action	8 years ago
Vicențiu Ciorbaru	8cee2f136d	MDEV-13384: "window" seems like a reserved column name but it's not listed as one Window is a reserved keyword according to SQL Standard 2016. However, we can make the grammar slightly flexible by allowing WINDOW keyword everywhere except table aliases. Change yacc grammar to separate between all keywords and table_alias keywords.	8 years ago
Alexander Barkov	9b53e541f0	MDEV-13788 Server crash when issuing bad SQL partition syntax	8 years ago
Andrei Elkin	aae4932775	MDEV-12012/MDEV-11969 Can't remove GTIDs for a stale GTID Domain ID As reported in MDEV-11969 "there's no way to ditch knowledge" about some domain that is no longer updated on a server. Besides being of annoyance to clutter output in DBA console stale domains can prevent the slave to connect the master as MDEV-12012 witnesses. What domain is obsolete must be evaluated by the user (DBA) according to whether the domain info is still relevant and will the domain ever receive any update. This patch introduces a method to discard obsolete gtid domains from the server binlog state. The removal requires no event group from such domain present in existing binlog files though. If there are any the containing logs must be first PURGEd in order for FLUSH BINARY LOGS DELETE_DOMAIN_ID=(list-of-domains) succeed. Otherwise the command returns an error. The list of obsolete domains can be computed through intersecting two sets - the earliest (first) binlog's Gtid_list and the current value of @@global.gtid_binlog_state - and extracting the domain id components from the intersection list items. The new DELETE_DOMAIN_ID featured FLUSH continues to rotate binlog omitting the deleted domains from the active binlog file's Gtid_list. Notice though when the command is ineffective - that none of requested to delete domain exists in the binlog state - rotation does not occur. Obsolete domain deletion is not harmful for connected slaves as long as master side binlog files purge is synchronized with FLUSH-DELETE_DOMAIN_ID. The slaves must have the last event from purged files processed as usual, in order not to bump later into requesting a gtid from a file which was already gone. While the command is not replicated (as ordinary FLUSH BINLOG LOGS is) slaves, even though having extra domains, won't suffer from reconnection errors thanks to master-slave gtid connection protocol allowing the master to be ignorant about a gtid domain. Should at failover such slave to be promoted into master role it may run the ex-master's FLUSH BINARY LOGS DELETE_DOMAIN_ID=(list-of-domains) to clean its own binlog state. NOTES. suite/perfschema/r/start_server_low_digest.result is re-recorded as consequence of internal parser codes changes.	8 years ago
Sergei Golubchik	d76f5774fe	MDEV-13459 Warnings, when compiling with gcc-7.x mostly caused by -Wimplicit-fallthrough	8 years ago
Vladislav Vaintroub	dc93ce8dea	Windows : Fix truncation warnings in sql/	8 years ago
Vladislav Vaintroub	7354dc6773	MDEV-13384 - misc Windows warnings fixed	8 years ago
Sergei Golubchik	d07daa3125	MDEV-13313 JSON type alias is insufficiently compatible make JSON an alias for LONGTEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_bin (same collation that item_jsonfunc.cc is using internally)	8 years ago
Sergei Golubchik	87f39bf824	MDEV-8659 Conflicting declaration is accepted: INT SIGNED ZEROFILL don't allow arbitrary combinations of SIGNED/UNSIGNED/ZEROFILL	8 years ago
Sergei Golubchik	1ea3c93fda	MDEV-9144 JSON data type for compatibility with MySQL, add 'JSON' as an alias for 'TEXT'	8 years ago
Sergei Golubchik	a6bef22cda	reduce grammar duplication	8 years ago
Sergei Golubchik	5c30fcfa2f	cleanup: C++ comments	8 years ago
Marko Mäkelä	71cd205956	Silence bogus GCC 7 warnings -Wimplicit-fallthrough Do not silence uncertain cases, or fix any bugs. The only functional change should be that ha_federated::extra() is not calling DBUG_PRINT to report an unhandled case for HA_EXTRA_PREPARE_FOR_DROP.	9 years ago
Marko Mäkelä	7972da8aa1	Silence bogus GCC 7 warnings -Wimplicit-fallthrough Do not silence uncertain cases, or fix any bugs. The only functional change should be that ha_federated::extra() is not calling DBUG_PRINT to report an unhandled case for HA_EXTRA_PREPARE_FOR_DROP.	9 years ago
Sergei Golubchik	22d8bb2706	MDEV-12421 Check constraint with query crashes server and renders DB unusable parse CHECK constraint before Column_definition validity checks	9 years ago
Marko Mäkelä	8805fe0d5c	Use %pure-parser instead of the deprecated %pure_parser.	9 years ago
Alexey Botchkov	fdeeab01c0	MDEV-6390 CONVERT TO CHARACTER SET utf8 doesn't change DEFAULT CHARSET. ALTER_CONVERT flag removed and replaced for ALTER_OPTIONS for the CONVERT TO CHARACTER SET command.	9 years ago
Sergei Golubchik	6f6d0531dc	MDEV-11439 No data type JSON, but CAST(something AS JSON) pretends to work Use JSON_COMPACT(X) instead of CAST(X AS JSON). Bonus - X is validated to be a valid JSON. Fix a typo in the error message.	9 years ago
Sergei Golubchik	e1f0f0dd06	Revert "MDEV-11439 No data type JSON, but CAST(something AS JSON) pretends to work" This reverts commit `1f372cf1de`. Wasn't supposed to be pushed just yet.	9 years ago
Sergei Golubchik	1f372cf1de	MDEV-11439 No data type JSON, but CAST(something AS JSON) pretends to work remove CAST(... AS JSON) from the grammar for 10.2.4	9 years ago
Sergei Golubchik	239790d92f	MDEV-11604 Assertion `!check_datetime_range(ltime)' failed in TIME_to_longlong_datetime_packed	9 years ago
Sergei Golubchik	1afb11074e	MDEV-11582 InnoDB: Failing assertion: !((field)->vcol_info && !(field)->stored_in_db()) change the parser not to allow SERIAL as a normal data type. make a special rule for it, where it could be used for define fields, but not generated fields, not return type of a stored function, etc.	9 years ago
Igor Babaev	8481c70ede	Fixed bug mdev-11867. If a window function with aggregation is over the result set of a grouping query then the argument of the aggregate function from the window function is allowed to be an aggregate function itself.	9 years ago
Igor Babaev	9073f9fd7d	Fixed bug mdev-9976. This bug happens due to a conflict in the construct window_spec. (win_ref conflicts with the non-reserved key word ROWS). The standard SQL-2003 says that ROWS is a reserved key word. Made this key word reserved in our grammar and removed the conflict.	9 years ago
Alexander Barkov	1d96b09890	MDEV-9979 Keywords UNBOUNDED, PRECEDING, FOLLOWING, TIES, OTHERS should be non-reserved Adding keywords the following keywords into the "keyword" rules: - EXCLUDE - UNBOUNDED - PRECEDING - FOLLOWING - TIES - OTHERS They are non-reserved words in the SQL standard (checked in a SQL-2011 draft), and they don't cause any conflicts in sql_yacc.yy.	9 years ago
Oleksandr Byelkin	bc4cac358e	MDEV-10035: DBUG_ASSERT on CREATE VIEW v1 AS SELECT * FROM t1 FOR UPDATE Ability to print lock type added. Restoring correct lock type for CREATE VIEW added.	9 years ago
Sergei Golubchik	ec6d8dadc0	reduce code duplication a little	9 years ago
Sergei Golubchik	8c876adfb6	Item_func_like: print a not like b instead of !(a like b)	9 years ago
Sergei Golubchik	6b0f4c24ab	cleanup: unpack_vcol_info_from_frm * do setup/cleanup for charset and arena only once per table not for every vcol * don't copy every vcol expression into table's memroot for parsing, do it in a temporary String buffer that is freed at the end * add asserts	9 years ago
Sergei Golubchik	a72f1deb2d	rename Virtual_column_info::expr_item now, when expr_str is gone, expr_item can be unambiguously renamed to expr.	9 years ago
Sergei Golubchik	a411d7f4f6	store/show vcols as item->print() otherwise we'd need to store sql_mode per vcol (consider CREATE INDEX...) and how SHOW CREATE TABLE would support that? Additionally, get rid of vcol::expr_str, just to make sure the string is always generated and never leaked in the original form.	9 years ago
Sergei Golubchik	a3614d33e8	cleanup: FOREIGN_KEY_INFO instead of returning strings for CASCADE/RESTRICT from every storage engine, use enum values	9 years ago
Sergei Golubchik	590d473760	cleanup: my_printf_error(ER_xxx, ER(ER_xxx), ... ) only use my_print_error when the error message is not ER(error_code)	9 years ago
Sergei Golubchik	0ed291e61c	cleanup: parser: s/USER/USER_SYM/	9 years ago
Sergei Golubchik	a721dcab8e	cleanup: Item_func_opt_neg::negate() remove redundant method	9 years ago
Sergei Golubchik	fd0044041b	don't convert WEEK(x) to WEEK(x, @@default_week_format)	9 years ago
Vicențiu Ciorbaru	eb4f2e063c	MDEV-11533: Roles with trailing white spaces are not cleared correctly Role names with trailing whitespaces are truncated in length as of `956e92d908` to fix MDEV-8609. The problem is that the code that creates role mappings expects the string to be null terminated. Add the null terminator to account for that as well. In the future the rest of the code can be cleaned up to never assume c style strings but only LEX_STRINGS.	9 years ago
Alexey Botchkov	486079d159	MDEV-11440 JSON has become a reserved word in MariaDB. 'JSON' made possible identifier.	9 years ago
Oleksandr Byelkin	098dff10ba	MDEV-11359 Implement IGNORE for bulk operation	9 years ago
Alexander Barkov	9bfde897c3	MDEV-11360 Dynamic SQL: DEFAULT as a bind parameter This patch adds DEFAULT as a possible dynamic SQL parameter, e.g.: EXECUTE IMMEDIATE 'INSERT INTO t1 (column) VALUES(?)' USING DEFAULT; EXECUTE IMMEDIATE 'UPDATE t1 SET column=?' USING DEFAULT; and for similar PREPARE..EXECUTE queries. This is done for symmetry with the STMT_INDICATOR_DEFAULT indicator in the client-server PS protocol. The changes include: - Allowing DEFAULT as a possible option in execute USING clause (sql_yacc.yy) - Adding "virtual bool Item::save_in_param(THD thd, Item_param param)", because "normal" items (that have real values) and Item_default_value have now different actions when assigning itself as an Item_param value. - Fixing switch() statements in a few Item_param methods not to have "default", because it was easy to forget to add a new "case" when adding a new XXX_VALUE value into the enum Item_param::enum_item_param_state. This is important, as we'll be adding new values soon, e.g. for MDEV-11359. Removing "default" helped to find and report bugs MDEV-11361 and MDEV-11362, because DECIMAL_VALUE is obviously not properly handled in some cases.	9 years ago
Alexey Botchkov	ebe5ebba16	MDEV-9143 JSON_xxx functions. The rest of mysql/json functions implemented. CAST AS JSON implemented.	9 years ago
Alexey Botchkov	27025221fe	MDEV-9143 JSON_xxx functions. strings/json_lib.c added as a JSON library. SQL frunction added with sql/item_jsonfunc.h/cc	9 years ago
Kristian Nielsen	19abe79fd1	MDEV-7145: Delayed replication, intermediate commit. Initial merge of delayed replication from MySQL git. The code from the initial push into MySQL is merged, and the associated test case passes. A number of tasks are still pending: 1. Check full test suite run for any regressions or .result file updates. 2. Extend the feature to also work for parallel replication. 3. There are some todo-comments about future refactoring left from MySQL, these should be located and merged on top. 4. There are some later related MySQL commits, these should be checked and merged. These include: `e134b9362b` `b38f0f7857` `fd2b210383` `afc397376e` 5. The testcase from MySQL relies heavily on sleep and timing for testing, and seems likely to sporadically fail on heavily loaded test servers in buildbot or distro build farms. Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>	9 years ago
Alexander Barkov	5058ced5df	MDEV-7769 MY_CHARSET_INFO refactoring# On branch 10.2 Part 3 (final): removing MY_CHARSET_HANDLER::well_formed_len().	9 years ago
Hartmut Holzgraefe	3234fafebf	MDEV-726 - CREATE and ALTER SERVER need to lowercase host name	9 years ago
Alexander Barkov	46dc7bdf1d	MDEV-10866 Extend PREPARE and EXECUTE IMMEDIATE to understand expressions MDEV-10867 PREPARE..EXECUTE is not consistent about non-ASCII characters	9 years ago
Alexander Barkov	e1a212ebbc	MDEV-10585 EXECUTE IMMEDIATE statement	9 years ago
Alexander Barkov	4c45b820aa	MDEV-10709 Expressions as parameters to Dynamic SQL	9 years ago
Monty	8be53a389c	MDEV-6112 multiple triggers per table This is similar to MysQL Worklog 3253, but with a different implementation. The disk format and SQL syntax is identical with MySQL 5.7. Fetures supported: - "Any" ammount of any trigger - Supports FOLLOWS and PRECEDES to be able to put triggers in a certain execution order. Implementation details: - Class Trigger added to hold information about a trigger. Before this trigger information was stored in a set of lists in Table_triggers_list and in Table_triggers_list::bodies - Each Trigger has a next field that poinst to the next Trigger with the same action and time. - When accessing a trigger, we now always access all linked triggers - The list are now only used to load and save trigger files. - MySQL trigger test case (trigger_wl3253) added and we execute these identically. - Even more gracefully handling of wrong trigger files than before. This is useful if a trigger file uses functions or syntax not provided by the server. - Each trigger now has a "Created" field that shows when the trigger was created, with 2 decimals. Other comments: - Many of the changes in test files was done because of the new "Created" field in the trigger file. This shows up in SHOW ... TRIGGER and when using information_schema.trigger. - Don't check if all memory is released if on uses --gdb; This is needed to be able to get a list from safemalloc of not freed memory while debugging. - Added option to trim_whitespace() to know how many prefix characters was skipped. - Changed a few ulonglong sql_mode to sql_mode_t, to find some wrong usage of sql_mode.	9 years ago
Igor Babaev	3b314ec633	Fixed bug mdev-10933. The bug was caused by a misplaced construct opt_with_clause for one of the variants of CREATE ... SELECT.	9 years ago

1 2 3 4 5 ...

5344 Commits (985d2d393c285ecd4539cb579b680f7b91fdaa1a)