Skip to main content

Altering Tables ( Modifying Columns )




One method to alter a column definition is to use a  MODIFY  clause.  The name of the column to be changed must be specified, followed by its new definition. Assume that the ID column's data type must be changed from  INT to  BIGINT, to allow the table to accommodate larger identification numbers.  In addition, the column needs to be changed to  UNSIGNED to disallow negative values.

The following statement accomplishes this task: 


ALTER TABLE eu_countries MODIFY new_population BIGINT(12) NOT NULL;

That ALTER TABLE statement changes the table structure as follows: 


+----------------------+-------------------+-------+------+----------+--------+ 
| Field                    | Type                | Null  | Key  | Default | Extra | 
+----------------------+-------------------+-------+------+----------+--------+ 
| name                   | char(52)          | NO   |         | NULL    |          | 
| new_population | decimal(12,0) | NO   |         | NULL    |          | 
+----------------------+-------------------+-------+------+-----------+------+ 


To disallow  NULL in the column, the column definition provided for  MODIFY must include the  NOT NULL attribute, even if the column was originally defined with NOT NULL.  This is true for other column attributes as well.  If they are not specified explicitly, the new definition won't carry them over from the old definition. 


The above ALTER TABLE/MODIFY statement changes the table row contents as follows: 


+----------------------------------+----------------------+ 
| name                                  | new_population | 
+----------------------------------+----------------------+ 
| Albania                              |        5101800      | 
| Andorra                             |         117000       | 
| Austria                               |       12137700    | 
| Belgium                             |       15358500    | 
| Bulgaria                             |       12286350    | 
| Bosnia and Herzegovina |        5958000     | 
:                        :                : 
+----------------------------------+----------------------+ 


Note:  MySQL will sometimes try to fit existing data in to the new datatype by applying data type conversions. 

Comments

Popular posts from this blog

PHP INTRODUCTION

                     PHP  (recursive acronym for  PHP: Hypertext Preprocessor ) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. PHP stands for  P HP:  H ypertext  P reprocessor PHP is a server-side scripting language, like ASP PHP scripts are executed on the server PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.) PHP is an open source software PHP is free to download and use Why PHP? PHP runs on different platforms (Windows, Linux, Unix, etc.) PHP is compatible with almost all servers used today (Apache, IIS, etc.) PHP is FREE to download from the official PHP resource:  www.php.net PHP is easy to learn and runs efficiently on the server side What can PHP do? Anything. PHP is mainly focused on server-side scripting, so you can...

Self Joins

A table name is always ambiguous when table is joined to itself using a self-join. For example, the Country table in the world database contains an IndepYear column indicating the year in which each country achieved independence. To find all countries that have the same year of independence as some given country, a self-join can be used. However, the query cannot be written like this: mysql> SELECT IndepYear, Name, Name -> FROM Country JOIN Country -> ON IndepYear = IndepYear AND Name = 'Qatar'; ERROR 1066 (42000): Not unique table/alias: 'Country' Furthermore, the ambiguity cannot be removed from column references by preceding them with table name qualifiers because the names remain identical: mysql> SELECT Country.IndepYear, Country.Name, Country.Name -> FROM Country JOIN Country -> ON Country.IndepYear = Country.IndepYear -> AND Country.Name = 'Qatar'; ERROR 1066 (42000): Not unique table/alias: 'Country' It ...