Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-9168

altering a column comment does a full copy

Details

    • 10.0.25

    Description

      Altering column's comment does a full table copy. It should be executed by only changing the frm.

      initial issue description follow

      This is a new feature request and is similar to this request. http://bugs.mysql.com/bug.php?id=64439

      We have multiple mariadb instances managing ~2.5T of our data. We decided to document them using table/column comments. Unfortunately, there isnt an easier way of doing this.

      1) Filed a bug regarding altering table comment doing full copy. MDEV-9103
      2) Changing the column comment does the full copy (MDEV-9168)
      3) Also, current syntax is error prone since you need to re-declare the data type (MDEV-9878)

      It would be nice to have the below:
      ALTER TABLE 'myTable' ALTER COLUMN `myField` ADD COMMENT 'a comment'

      Instead of:
      ALTER TABLE `myTable` CHANGE `myField` `myField` varchar(20) NOT NULL COMMENT 'my comment'

      I agree that comments work great, if we have them created while creating the table. But, its almost impossible to update/add them at the later stage for the bigger tables in the production.

      Is there a better way of documenting the tables instead of using comments ? Please let me know.

      Thanks.

      -Bala

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-9103 Altering table comment does a full copy

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-9878 Awkward syntax for altering the column comments

          • Major - Major loss of function.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            bala.linux Bala created issue -
            bala.linux Bala made changes -
            Field Original Value New Value
            Issue Type Task [ 3 ] Epic [ 5 ]
            serg Sergei Golubchik made changes -
            Description This is a new feature request and is similar to this request. http://bugs.mysql.com/bug.php?id=64439

            We have multiple mariadb instances managing ~2.5T of our data. We decided to document them using table/column comments. Unfortunately, there isnt an easier way of doing this.

            1) Filed a bug regarding altering table comment doing full copy. https://mariadb.atlassian.net/browse/MDEV-9103
            2) Changing the column comment does the full copy.
            3) Also, current syntax is error prone since you need to re-declare the data type.

            It would be nice to have the below:
            ALTER TABLE 'myTable' ALTER COLUMN `myField` ADD COMMENT 'a comment'

            Instead of:
            ALTER TABLE `myTable` CHANGE `myField` `myField` varchar(20) NOT NULL COMMENT 'my comment'

            I agree that comments work great, if we have them created while creating the table. But, its almost impossible to update/add them at the later stage for the bigger tables in the production.

            Is there a better way of documenting the tables instead of using comments ? Please let me know.

            Thanks.

            -Bala             		This is a new feature request and is similar to this request. http://bugs.mysql.com/bug.php?id=64439

            We have multiple mariadb instances managing ~2.5T of our data. We decided to document them using table/column comments. Unfortunately, there isnt an easier way of doing this.

            1) Filed a bug regarding altering table comment doing full copy. MDEV-9103
            2) Changing the column comment does the full copy.
            3) Also, current syntax is error prone since you need to re-declare the data type.

            It would be nice to have the below:
            ALTER TABLE 'myTable' ALTER COLUMN `myField` ADD COMMENT 'a comment'

            Instead of:
            ALTER TABLE `myTable` CHANGE `myField` `myField` varchar(20) NOT NULL COMMENT 'my comment'

            I agree that comments work great, if we have them created while creating the table. But, its almost impossible to update/add them at the later stage for the bigger tables in the production.

            Is there a better way of documenting the tables instead of using comments ? Please let me know.

            Thanks.

            -Bala
            serg Sergei Golubchik made changes -
            Issue Type Epic [ 5 ] Task [ 3 ]
            bala.linux Bala made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Issue Type Task [ 3 ] Bug [ 1 ]
            serg Sergei Golubchik made changes -
            Affects Version/s 10.0 [ 16000 ]
            Affects Version/s 10.1 [ 16100 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.0 [ 16000 ]
            Fix Version/s 10.1 [ 16100 ]
            serg Sergei Golubchik made changes -
            Description This is a new feature request and is similar to this request. http://bugs.mysql.com/bug.php?id=64439

            We have multiple mariadb instances managing ~2.5T of our data. We decided to document them using table/column comments. Unfortunately, there isnt an easier way of doing this.

            1) Filed a bug regarding altering table comment doing full copy. MDEV-9103
            2) Changing the column comment does the full copy.
            3) Also, current syntax is error prone since you need to re-declare the data type.

            It would be nice to have the below:
            ALTER TABLE 'myTable' ALTER COLUMN `myField` ADD COMMENT 'a comment'

            Instead of:
            ALTER TABLE `myTable` CHANGE `myField` `myField` varchar(20) NOT NULL COMMENT 'my comment'

            I agree that comments work great, if we have them created while creating the table. But, its almost impossible to update/add them at the later stage for the bigger tables in the production.

            Is there a better way of documenting the tables instead of using comments ? Please let me know.

            Thanks.

            -Bala             		Altering column's comment does a full table copy. It should be executed by only changing the frm.

            *initial issue description follow*
            {quote}This is a new feature request and is similar to this request. http://bugs.mysql.com/bug.php?id=64439

            We have multiple mariadb instances managing ~2.5T of our data. We decided to document them using table/column comments. Unfortunately, there isnt an easier way of doing this.

            1) Filed a bug regarding altering table comment doing full copy. MDEV-9103
            2) Changing the column comment does the full copy.
            3) Also, current syntax is error prone since you need to re-declare the data type.

            It would be nice to have the below:
            ALTER TABLE 'myTable' ALTER COLUMN `myField` ADD COMMENT 'a comment'

            Instead of:
            ALTER TABLE `myTable` CHANGE `myField` `myField` varchar(20) NOT NULL COMMENT 'my comment'

            I agree that comments work great, if we have them created while creating the table. But, its almost impossible to update/add them at the later stage for the bigger tables in the production.

            Is there a better way of documenting the tables instead of using comments ? Please let me know.

            Thanks.

            -Bala{quote}
            serg Sergei Golubchik made changes -
            Description Altering column's comment does a full table copy. It should be executed by only changing the frm.

            *initial issue description follow*
            {quote}This is a new feature request and is similar to this request. http://bugs.mysql.com/bug.php?id=64439

            We have multiple mariadb instances managing ~2.5T of our data. We decided to document them using table/column comments. Unfortunately, there isnt an easier way of doing this.

            1) Filed a bug regarding altering table comment doing full copy. MDEV-9103
            2) Changing the column comment does the full copy.
            3) Also, current syntax is error prone since you need to re-declare the data type.

            It would be nice to have the below:
            ALTER TABLE 'myTable' ALTER COLUMN `myField` ADD COMMENT 'a comment'

            Instead of:
            ALTER TABLE `myTable` CHANGE `myField` `myField` varchar(20) NOT NULL COMMENT 'my comment'

            I agree that comments work great, if we have them created while creating the table. But, its almost impossible to update/add them at the later stage for the bigger tables in the production.

            Is there a better way of documenting the tables instead of using comments ? Please let me know.

            Thanks.

            -Bala{quote}             		Altering column's comment does a full table copy. It should be executed by only changing the frm.

            *initial issue description follow*
            {quote}This is a new feature request and is similar to this request. http://bugs.mysql.com/bug.php?id=64439

            We have multiple mariadb instances managing ~2.5T of our data. We decided to document them using table/column comments. Unfortunately, there isnt an easier way of doing this.

            1) Filed a bug regarding altering table comment doing full copy. MDEV-9103
            2) Changing the column comment does the full copy (MDEV-9168)
            3) Also, current syntax is error prone since you need to re-declare the data type (MDEV-9878)

            It would be nice to have the below:
            ALTER TABLE 'myTable' ALTER COLUMN `myField` ADD COMMENT 'a comment'

            Instead of:
            ALTER TABLE `myTable` CHANGE `myField` `myField` varchar(20) NOT NULL COMMENT 'my comment'

            I agree that comments work great, if we have them created while creating the table. But, its almost impossible to update/add them at the later stage for the bigger tables in the production.

            Is there a better way of documenting the tables instead of using comments ? Please let me know.

            Thanks.

            -Bala{quote}
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Summary Easy/faster way to update column comments. altering a column comment does a full copy
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Sprint 10.0.25 [ 50 ]
            serg Sergei Golubchik made changes -
            Rank Ranked lower
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            serg Sergei Golubchik made changes -
            Status In Progress [ 3 ] Stalled [ 10000 ]
            serg Sergei Golubchik made changes -
            Labels need_feedback
            serg Sergei Golubchik made changes -
            Fix Version/s 10.0.25 [ 21701 ]
            Fix Version/s 10.1.14 [ 21804 ]
            Fix Version/s 10.0 [ 16000 ]
            Fix Version/s 10.1 [ 16100 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            julien.fritsch Julien Fritsch made changes -
            Labels need_feedback
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 72702 ] MariaDB v4 [ 149853 ]

            People

              serg Sergei Golubchik
              bala.linux Bala
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.