An error occurred fetching the project authors.
  1. 27 May, 2008 1 commit
    • Patrick Crews's avatar
      Bug#36721 - Test funcs1.<engine>_func_view failing for multiple engines · e856d953
      Patrick Crews authored
      Bug#36724 - Test funcs_1.<engine>_storedproc_02 needs to be updated
      Bug#36726 - Test funcs_1.<engine>_storedproc failing - Needs to be updated on 5.1+
      
      func_view bug:  re-records .result files to account for addition of charset and collation data 
                      to SHOW CREATE VIEW output
      storedproc bugs:  Added expected errors for those storedprocs that use SQLSTATE:00000
                        in their handlers.  re-recorded .result files to account for these
                        expected errors.
      e856d953
  2. 23 Apr, 2008 1 commit
    • kent@mysql.com/kent-amd64.(none)'s avatar
      Many files: [Changes done by mleich] · 3cf72be6
      kent@mysql.com/kent-amd64.(none) authored
        Fix for
           Bug#35335 funcs_1: Some tests fail within load_file during
                              pushbuild runs
           Solution: 1. Move files with input data used in load_file,
                        load data etc.
                        from suite/funcs_1/<whatever>
                        to std_data
                     2. Use for testsuite funcs_1 the server option
                        --secure-file-priv=<MYSQLTEST_VARDIR>
                     3. Outfiles have to be stored under MYSQLTEST_VARDIR
        + changes according to WL#4304 Cleanup in funcs_1 tests
          - backport of fixes/improvements made in 5.1 to 5.0
            The differences between scripts in 5.0 and 5.1 cause
            much additional and annoying work during any upmerge.
          - replace error numbers with names
          - improved comments
          - improved formatting
          - Unify storage engine names so that result files for
            storage engine variants do not differ (some tests)
          - remove a script no more used (tests are done in other scripts)
      3cf72be6
  3. 01 Apr, 2008 2 commits
    • mleich@five.local.lan's avatar
      Fixes for failing funcs_1 tests in mysql-5.1.24-rc · 1f26fe08
      mleich@five.local.lan authored
      Problems were caused by modifications of
      - the server
        - HANDLER FOR SQLSTATE '00000' is now rejected (bug fix)
          affects several ..._storedproc* tests
        - improved error message
          affects the ..._trig_03e
        - improved content of information_schema.COLUMNS about
          information_schema.REFERENTIAL_CONSTRAINTS
          affects is_columns_is
      - the content of the community build (collations)
          affects charset_collation_3 
      1f26fe08
    • mleich@five.local.lan's avatar
      Post merge fix for · 414299f4
      mleich@five.local.lan authored
         ChangeSet@1.2583, 2008-03-31
         Merge five.local.lan:/work/merge/mysql-5.0-Bug
         into  five.local.lan:/work/merge/mysql-5.1-Bug
         Addditional manual fixes will be needed.
         MERGE: 1.1810.3667.16
      
         Which contains
            ChangeSet@1.1810.3667.16, 2008-03-31
            Fix for Bug
              #35335 funcs_1: Some tests fail within load_file during
                              pushbuild runs
         ...
      414299f4
  4. 31 Mar, 2008 1 commit
    • mleich@five.local.lan's avatar
      Fix for · 89ddc0aa
      mleich@five.local.lan authored
         Bug#35335 funcs_1: Some tests fail within load_file during
                            pushbuild runs
         Solution: 1. Move files with input data used in load_file, 
                      load data etc. 
                      from suite/funcs_1/<whatever>
                      to std_data
                   2. Use for testsuite funcs_1 the server option
                      --secure-file-priv=<MYSQLTEST_VARDIR>
                   3. Outfiles have to be stored under MYSQLTEST_VARDIR 
      + changes according to WL#4304 Cleanup in funcs_1 tests
        - backport of fixes/improvements made in 5.1 to 5.0
          The differences between scripts in 5.0 and 5.1 cause
          much additional and annoying work during any upmerge.
        - replace error numbers with names
        - improved comments
        - improved formatting
        - Unify storage engine names so that result files for
          storage engine variants do not differ (some tests)
        - remove a script no more used (tests are done in other scripts)
      89ddc0aa
  5. 11 Mar, 2008 1 commit
    • mleich@five.local.lan's avatar
      Post fix for · d7e6ba47
      mleich@five.local.lan authored
      WL#4203 Reorganize and fix the data dictionary tests of
              testsuite funcs_1
      because the goal to fix
      Bug#34532 Some funcs_1 tests do not clean up at end of testing
      was partially missed.
      Some minor additional modifications are for
         WL#4304 Cleanup in funcs_1 tests
      d7e6ba47
  6. 07 Mar, 2008 2 commits
    • mleich@five.local.lan's avatar
      Post merge fixes after · 40c0b4c3
      mleich@five.local.lan authored
      ChangeSet@1.2561, 2008-03-07 17:44:03+01:00, mleich@five.local.lan +132 -0
        Merge five.local.lan:/work/merge/mysql-5.0-funcs_1
        into  five.local.lan:/work/merge/mysql-5.1-funcs_1
        MERGE: 1.1810.3473.24
      
      ChangeSet@1.1810.3473.24, 2008-03-07
        WL#4203 Reorganize and fix the data dictionary tests of
                testsuite funcs_1
      
        1. Adjustment of expected results to modified server properties
        2. Add some tests of information_schema views
        3. Minor corrections and improvements
      40c0b4c3
    • mleich@five.local.lan's avatar
      WL#4203 Reorganize and fix the data dictionary tests of · 30091e23
      mleich@five.local.lan authored
              testsuite funcs_1
      1. Fix the following bugs
         Bug#30440 "datadict" tests (all engines) fail: Character sets depend on configuration
            Solution: Test variants charset_collation_* adjusted to different builds
         Bug#32603 "datadict" tests (all engines) fail in "community" tree: "PROFILING" table
            Solution: Excluding "PROFILING" table from queries
         Bug#33654 "slow log" is missing a line
            Solution: Unify the content of the fields TABLES.TABLE_ROWS and
                      STATISTICS.CARDINALITY within result sets
         Bug#34532 Some funcs_1 tests do not clean up at end of testing
            Solution: DROP objects/reset global server variables modified during testing
                      + let tests missing implementation end before loading of tables
         Bug#31421 funcs_1: ndb__datadict fails, discrepancy between scripts and expected results
            Solution: Cut <engine>__datadict tests into smaller tests + generate new results.
         Bug#33599 INFORMATION_SCHEMA.STATISTICS got a new column INDEX_COMMENT: tests fail (2)
            Generation of new results during post merge fix
         Bug#33600 CHARACTER_OCTET_LENGTH is now CHARACTER_MAXIMUM_LENGTH * 4
            Generation of new results during post merge fix
         Bug#33631 Platform-specific replace of CHARACTER_MAXIMUM_LENGTH broken by 4-byte encoding
            Generation of new results during post merge fix
            + removal of platform-specific replace routine (no more needed)
      2. Restructure the tests
         - Test not more than one INFORMATION_SCHEMA view per testscript
         - Separate tests of I_S view layout+functionality from content related to the
           all time existing databases "information_schema", "mysql" and "test"
         - Avoid storage engine related variants of tests which are not sensible to
           storage engines at all.
      3. Reimplement or add some subtests + cleanup
         There is a some probability that even the reviewed changeset
         - does not fix all bugs from above   or
         - contains new bugs which show up on some platforms <> Linux or on one of
           the various build types
      4. The changeset contains fixes according to
         - one code review
         - minor bugs within testing code found after code review (accepted by reviewer)
         - problems found during tests with 5.0.56 in build environment
      30091e23
  7. 27 Jul, 2007 2 commits
  8. 06 Feb, 2007 2 commits