qwerin / fusion-tables

Automatically exported from code.google.com/p/fusion-tables
0 stars 1 forks source link

Extended definition of a computed column #1314

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What new feature would you like to see implemented? How will you use it?

Would like the computed column in a fusion table to have rich logic like those 
in SQL Server. The current limitation is very severe, allowing only numeric 
values.

Microsoft defines the computed column expression as 

computed_column_expression

Is an expression that defines the value of a computed column. A computed column 
is a virtual column that is not physically stored in the table but is computed 
from an expression that uses other columns in the same table. For example, a 
computed column could have the definition: cost AS price * qty. The expression 
can be a noncomputed column name, constant, function, variable, and any 
combination of these connected by one or more operators. The expression cannot 
be a subquery or include an alias data type.
Computed columns can be used in select lists, WHERE clauses, ORDER BY clauses, 
or any other locations where regular expressions can be used, but with the 
following exceptions:
A computed column cannot be used as a DEFAULT or FOREIGN KEY constraint 
definition or with a NOT NULL constraint definition. However, if the computed 
column value is defined by a deterministic expression and the data type of the 
result is allowed in index columns, a computed column can be used as a key 
column in an index or as part of any PRIMARY KEY or UNIQUE constraint.
For example, if the table has integer columns a and b, the computed column a + 
b may be indexed, but computed column a + DATEPART(dd, GETDATE()) cannot be 
indexed, because the value might change in subsequent invocations.
A computed column cannot be the target of an INSERT or UPDATE statement.

--------------------------------------------------------------------------
NOTE: Use this form to suggest new features for Google Fusion Tables
website or API.  For BUGS, please e-mail us at googletables-
feedback@google.com.

Your "star" vote on requests in this issue tracker helps the Fusion Tables
team prioritize work on the most useful features.

By submitting this form you agree to the Google Terms of Service
(http://www.google.com/accounts/TOS) and the following additional term:
In addition to the Content license you grant to Google in Section 11 of the
Google Terms of Service, you agree that Google may, at its option, use your
Content to provide support for, or to develop, correct or improve Google's
current or future products and services, without any compensation to you.

Thanks for the suggestion!
--------------------------------------------------------------------------

Original issue reported on code.google.com by wjho...@gmail.com on 9 Oct 2013 at 6:12

GoogleCodeExporter commented 9 years ago

Original comment by rmcch...@google.com on 28 Dec 2013 at 1:39