An error occurred fetching the project authors.
- 22 Dec, 2010 1 commit
-
-
Mattias Jonsson authored
Bug#57071: EXTRACT(WEEK from date_col) cannot be allowed as partitioning function There were functions allowed as partitioning functions that implicit allowed cast. That could result in unacceptable behaviour. Solution was to check that the arguments of date and time functions have allowed types (field and date/datetime/time depending on function).
-
- 01 Oct, 2010 2 commits
-
-
Mattias Jonsson authored
-
Mattias Jonsson authored
-
- 22 Sep, 2010 1 commit
-
-
Alexey Kopytov authored
Fixed a number of memory leaks discovered by valgrind.
-
- 30 Aug, 2010 1 commit
-
-
Mattias Jonsson authored
It was hard to understand what the error really meant. The error checking in partitioning is done in several different parts during the execution of a query which can make it hard to return useful errors. Added a new error for bad VALUES part in the per PARTITION clause. Using the more verbose error that a column is not allowed in the partitioning function instead of just that the function is not allowed.
-
- 25 May, 2010 1 commit
-
-
Mattias Jonsson authored
Problem was reporting wrong error Fixed by adding a new error which better explain the problem.
-
- 11 Mar, 2010 1 commit
-
-
Mattias Jonsson authored
There was no check for DATA/INDEX DIRECTORY for subpartitions Added the same check as for partitions.
-
- 04 Mar, 2010 1 commit
-
-
Mattias Jonsson authored
auto_increment on duplicate entry The bug was that when INSERT_ID was used and the storage engine was told to release any reserved but not used auto_increment values, it set the highest auto_increment value to INSERT_ID. The fix was to check if the auto_increment value was forced by user (INSERT_ID) or by slave-thread, i.e. not auto- generated. So that it is only allowed to release generated values.
-
- 13 Dec, 2009 1 commit
-
-
Alexey Kopytov authored
timestamp primary key Since TIMESTAMP values are adjusted by the current time zone settings in both numeric and string contexts, using any expressions involving TIMESTAMP values as a (sub)partitioning function leads to undeterministic behavior of partitioned tables. The effect may vary depending on a storage engine, it can be either incorrect data being retrieved or stored, or an assertion failure. The root cause of this is the fact that the calculated partition ID may differ from a previously calculated ID for the same data due to timezone adjustments of the partitioning expression value. Fixed by disabling any expressions involving TIMESTAMP values to be used in partitioning functions with the follwing two exceptions: 1. Creating or altering into a partitioned table that violates the above rule is not allowed, but opening existing such tables results in a warning rather than an error so that such tables could be fixed. 2. UNIX_TIMESTAMP() is the only way to get a timezone-independent value from a TIMESTAMP column, because it returns the internal representation (a time_t value) of a TIMESTAMP argument verbatim. So UNIX_TIMESTAMP(timestamp_column) is allowed and should be used to fix existing tables if one wants to use TIMESTAMP columns with partitioning.
-
- 11 Dec, 2009 1 commit
-
-
Mattias Jonsson authored
with temporary table and partitions It was possible to create temporary partitioned tables via create table ... like ... (which is not allowed with create temporary table). This lead to a new HA_EXTRA flag (HA_EXTRA_MMAP) was sent to the partitioning handler, which was caught on an assert in debug builds. Solution was to check for partitioned tables when doing create table ... like ... and disallow it.
-
- 21 Oct, 2009 1 commit
-
-
Mikael Ronstrom authored
-
- 18 Feb, 2009 1 commit
-
-
Mattias Jonsson authored
handler::get_dup_key used the called handler for the info call, but used table->file handler for errkey. Fixed by using table->file->info instead.
-
- 25 Feb, 2008 1 commit
-
-
mattiasj@witty. authored
Fixed a missed case in the patch for Bug#31931. Also makes Bug#33722 a duplicate of Bug#31931. Added tests for better coverage. Replaced some legacy function calls.
-
- 12 Dec, 2007 1 commit
-
-
msvensson@pilot.mysql.com authored
- dynamic configuration support - safe process - cleanups - create new suite for fedarated
-
- 10 Nov, 2007 1 commit
-
-
mattiasj@mattiasj-laptop.(none) authored
Problem: there was no standard syntax error when creating partitions with syntax error in the partitioning clause. Solution: added "Syntax error: " to the error message
-
- 13 Jun, 2007 1 commit
-
-
mikael@dator6.(none) authored
-
- 04 Apr, 2007 1 commit
-
-
mikron@mikael-ronstr-ms-dator.local authored
-
- 08 Sep, 2006 1 commit
-
-
mikael/pappa@dator5.(none) authored
-
- 02 Aug, 2006 1 commit
-
-
mikael/pappa@dator5.(none) authored
ascii on varchar now allowed
-
- 31 Jul, 2006 1 commit
-
-
mikael/pappa@dator5.(none) authored
-
- 21 Jun, 2006 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
-
- 20 Jun, 2006 2 commits
-
-
mikael@dator5.(none) authored
New test cases
-
mikael@dator5.(none) authored
-
- 14 Jun, 2006 1 commit
-
-
- 05 Jun, 2006 1 commit
-
-
- 31 May, 2006 1 commit
-
-
BUG#18198: Many strange partition functions were allowed, now only strictly allowed functions are ok
-
- 18 Apr, 2006 1 commit
-
-
- 17 Jan, 2006 1 commit
-
-
Optimised version of ADD/DROP/REORGANIZE partitions for non-NDB storage engines. New syntax to handle REBUILD/OPTIMIZE/ANALYZE/CHECK/REPAIR partitions Quite a few bug fixes
-
- 15 Dec, 2005 1 commit
-
-
holyfoot@deer.(none) authored
-
- 22 Jul, 2005 1 commit
-
-
- 20 Jul, 2005 1 commit
-
-
tulin@dl145b.mysql.com authored
-
- 18 Jul, 2005 1 commit
-
-
mronstrom@mysql.com authored
-