An error occurred fetching the project authors.
  1. 28 Mar, 2017 1 commit
  2. 10 Feb, 2017 4 commits
  3. 31 Jan, 2017 1 commit
  4. 15 Jan, 2017 1 commit
  5. 05 Dec, 2016 1 commit
  6. 03 Nov, 2016 1 commit
  7. 23 Oct, 2016 1 commit
  8. 25 Sep, 2016 1 commit
  9. 16 Sep, 2016 3 commits
  10. 31 Aug, 2016 3 commits
  11. 11 Aug, 2016 1 commit
  12. 14 Jul, 2016 1 commit
  13. 02 Jul, 2016 1 commit
  14. 30 Jun, 2016 2 commits
    • Igor Babaev's avatar
    • Michael Widenius's avatar
      MDEV-7563 Support CHECK constraint as in (or close to) SQL Standard · db7edfed
      Michael Widenius authored
      MDEV-10134 Add full support for DEFAULT
      
      - Added support for using tables with MySQL 5.7 virtual fields,
        including MySQL 5.7 syntax
      - Better error messages also for old cases
      - CREATE ... SELECT now also updates timestamp columns
      - Blob can now have default values
      - Added new system variable "check_constraint_checks", to turn of
        CHECK constraint checking if needed.
      - Removed some engine independent tests in suite vcol to only test myisam
      - Moved some tests from 'include' to 't'. Should some day be done for all tests.
      - FRM version increased to 11 if one uses virtual fields or constraints
      - Changed to use a bitmap to check if a field has got a value, instead of
        setting HAS_EXPLICIT_VALUE bit in field flags
      - Expressions can now be up to 65K in total
      - Ensure we are not refering to uninitialized fields when handling virtual fields or defaults
      - Changed check_vcol_func_processor() to return a bitmap of used types
      - Had to change some functions that calculated cached value in fix_fields to do
        this in val() or getdate() instead.
      - store_now_in_TIME() now takes a THD argument
      - fill_record() now updates default values
      - Add a lookahead for NOT NULL, to be able to handle DEFAULT 1+1 NOT NULL
      - Automatically generate a name for constraints that doesn't have a name
      - Added support for ALTER TABLE DROP CONSTRAINT
      - Ensure that partition functions register virtual fields used. This fixes
        some bugs when using virtual fields in a partitioning function
      db7edfed
  15. 29 Jun, 2016 1 commit
  16. 22 Jun, 2016 1 commit
    • Monty's avatar
      MDEV-10138 Support for decimals up to 38 digits · 34eb10e4
      Monty authored
      Decimals with float, double and decimal now works the following way:
      
      - DECIMAL_NOT_SPECIFIED is used when declaring DECIMALS without a firm number
        of decimals.  It's only used in asserts and my_decimal_int_part.
      - FLOATING_POINT_DECIMALS (31) is used to mark that a FLOAT or DOUBLE
        was defined without decimals. This is regarded as a floating point value.
      - Max decimals allowed for FLOAT and DOUBLE is FLOATING_POINT_DECIMALS-1
      - Clients assumes that float and double with decimals >= NOT_FIXED_DEC are
        floating point values (no decimals)
      - In the .frm decimals=FLOATING_POINT_DECIMALS are used to define
        floating point for float and double (31, like before)
      
      To ensure compatibility with old clients we do:
      
      - When storing float and double, we change NOT_FIXED_DEC to
        FLOATING_POINT_DECIMALS.
      - When creating fields from .frm we change for float and double
        FLOATING_POINT_DEC to NOT_FIXED_DEC
      - When sending definition for a float/decimal field without decimals
        to the client as part of a result set we convert NOT_FIXED_DEC to
        FLOATING_POINT_DECIMALS.
      - variance() and std() has changed to limit the decimals to
        FLOATING_POINT_DECIMALS -1 to not get the double converted floating point.
        (This was to preserve compatiblity)
      - FLOAT and DOUBLE still have 30 as max number of decimals.
      
      Bugs fixed:
      
      variance() printed more decimals than we support for double values.
      
      New behaviour:
      - Strings now have 38 decimals instead of 30 when converted to decimal
      - CREATE ... SELECT with a decimal with > 30 decimals will create a column
        with a smaller range than before as we are trying to preserve the number of
        decimals.
      
      
      Other changes
      - We are now using the obsolete bit FIELDFLAG_LEFT_FULLSCREEN to specify
        decimals > 31
      - NOT_FIXED_DEC is now declared in one place
      - For clients, NOT_FIXED_DEC is always 31 (to ensure compatibility).
        On the server NOT_FIXED_DEC is DECIMAL_NOT_SPECIFIED (39)
      - AUTO_SEC_PART_DIGITS is taken from DECIMAL_NOT_SPECIFIED
      - DOUBLE conversion functions are now using DECIMAL_NOT_SPECIFIED instead of
        NOT_FIXED_DEC
      34eb10e4
  17. 03 Jun, 2016 1 commit
  18. 20 May, 2016 1 commit
  19. 24 Mar, 2016 1 commit
  20. 23 Mar, 2016 1 commit
  21. 22 Mar, 2016 1 commit
  22. 08 Mar, 2016 1 commit
  23. 25 Jan, 2016 1 commit
  24. 24 Nov, 2015 1 commit
  25. 23 Sep, 2015 1 commit
  26. 22 Sep, 2015 1 commit
  27. 04 Sep, 2015 2 commits
  28. 30 Jun, 2015 1 commit
  29. 27 Jun, 2015 1 commit
  30. 02 Jun, 2015 1 commit
  31. 01 Jun, 2015 1 commit