未加星标

Understanding Generated Columns

字体大小 | |
[数据库(mysql) 所属分类 数据库(mysql) | 发布者 店小二05 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏
The Theory

Generated Columns is a feature released on mysql 5.7. They can be used during CREATE TABLE or ALTER TABLE statements. It is a way of storing data without actually sending it through the INSERT or UPDATE clauses in SQL. The database resolves what the data will be.

There are two types of Generated Columns: Virtual and Stored . They work with:

mathematical expressions ( product_price * quantity ) built-in functions ( RIGHT() , CONCAT() , FROM_UNIXTIME() , JSON_EXTRACT() ) literals (“2”, “new”, 0)

Besides that, they can be indexed but they don’t allow subqueries in it.

A Generated Column works within the table domain. If you need subqueries on a particular column, you may have to look at Views .

The basic example

As an example I am going to use an e-commerce database as based on my past experience of what I have seen and worked. You will probably have at least these tables or something similar:

users stores user info products stores product info like price and description orders stores the user_id, date of order orders_items stores product_id, order_id, quantity and price at the time of purchase

This is the whole DB: Gist .

Notice the order_items definition:

The retrieval would bring:

id order_id product_id product_price quantity 1 369 1304 202.18 7 2 4 1736 250.40 3 3 270 1404 29.89 5 4 256 179 190.40 10 5 107 1911 146.98 1

One example is to get the total of that order_item row, something like total_item_price that would store the value of product_price * quantity to show how much the summed amount of an item would be. Some databases have the MONEY type to store price , as with MySQL it is recommended to work with DECIMAL .

People solve this problem in different ways:

store the calculated price on a new column to make it easier to retrieve; create a view; or they calculate in the application itself, which in this case might cause problems due to how the language handles floats. There are libraries to deal with money values in a lot of languages and frameworks, however, the overhead of converting each row into a money object could be costly depending on the amount of data being transferred.

Another way I’ve seen is: people calculate in the query the total amount for the orders_items row as product_price * quantity :

id order_id product_id product_price quantity total_item_price 1 369 1304 202.18 7 1415.26 2 4 1736 250.40 3 751.20 3 270 1404 29.89 5 149.45 4 256 179 190.40 10 1904.00 5 107 1911 146.98 1 146.98 Virtual Columns They take no disk space, except when using a Virtual Column as in a Secondary Index . They are an INPLACE operation: it means the table definition is changed without having to recopy all the data again. More info . The values are calculated on the fly during read operations and BEFORE triggers.

Consider using virtual columns for data where changes happens in a significant number of times. The cost of a Virtual Column comes from reading a table constantly and the server has to compute every time what that column value will be.

Stored Columns They do use disk space. It has the same cost of adding a new column, so it is a COPY operation Values are updated in every INSERT and UPDATE statement.

You should consider using Stored Columns for when the data doesn’t change significantly or at all after creation, like for instance, the example above with the orders_items table. Once a purchase is made, the price of the product is stored, not being changed, neither the quantity. Considering this information we could create total_item_price as a Stored Column.

The code Creating a table -- Virtual Column CREATE TABLE `orders_items` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `order_id` int(10) unsigned NOT NULL, `product_id` int(10) unsigned NOT NULL, `product_price` decimal(10,2) unsigned NOT NULL DEFAULT '0.00', `quantity` int(10) unsigned NOT NULL DEFAULT 1, `total_item_price` decimal(10,2) AS (`quantity` * `product_price`), `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, `updated_at` varchar(45) NOT NULL DEFAULT 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP', PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4; -- Stored Column CREATE TABLE `orders_items` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `order_id` int(10) unsigned NOT NULL, `product_id` int(10) unsigned NOT NULL, `product_price` decimal(10,2) unsigned NOT NULL DEFAULT '0.00', `quantity` int(10) unsigned NOT NULL DEFAULT 1, `total_item_price` decimal(10,2) AS (`quantity` * `product_price`) STORED, `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, `updated_at` varchar(45) NOT NULL DEFAULT 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP', PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4;

Notice how the definition changes on line 9 and 23: you have another keyword, AS , then an expression and specifically on line 23 you see a STORED keyword. In both lines they are generated columns, if nothing is specified will be a VIRTUAL column.

Altering a table

It uses the same syntax as adding a column, just adding the “ AS ( expression )” after the data type:

-- `full_name` as VIRTUAL COLUMN ALTER TABLE users ADD COLUMN `full_name` VARCHAR(500) AS (CONCAT_WS(" ", `first_name`, `last_name`)); -- `total_item_price` as STORED COLUMN ALTER TABLE orders_items ADD COLUMN `total_item_price` DECIMAL(10, 2) AS (`quantity` * `product_price`) STORED; JSON fields

It is also possible to extract data from JSON fields using generated columns. As the functions for JSON are built-in, JSON_EXTRACT and JSON_UNQUOTE as well “ -> ” and “ ->> ” work as expressions for a generated column:

-- Stored Columns ALTER TABLE `twitter_users` ADD COLUMN `location` VARCHAR(255) AS (response->>"$.location") STORED; Final considerations

When the type is STORED , it must be specified after the expression otherwise the default behaviour will be to be VIRTUAL .

Generated columns can have indexes created as the following, no matter if stored, virtual or extracted from a JSON field:

ALTER TABLE users ADD INDEX `ix_full_name` (`full_name`);

Which is the same syntax for normal columns.

本文数据库(mysql)相关术语:navicat for mysql mysql workbench mysql数据库 mysql 存储过程 mysql安装图解 mysql教程 mysql 管理工具

主题: SQLAUMySQLInnoDBCUTIAUTUTUARY
分页:12
转载请注明
本文标题:Understanding Generated Columns
本站链接:http://www.codesec.net/view/484919.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 数据库(mysql) | 评论(0) | 阅读(30)