Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
Compatibility-1
Description
Add full support for DEFAULT
- Support for functions: DEFAULT (1+1)
- Referring to previous fields in the table
- Support for DEFAULT for blobs
In addition this task will lift the current restrictions for virtual columns:
- Non stored virtual columns can have almost any expression (including constant expression)
- No 300 character limit. (Limit is 64K for all stored expressions + column definitions)
Example:
create table t1 (a bigint default uuid_short(), b blob DEFAULT "look at me!" NOT NULL);
Attachments
Issue Links
- includes
-
MDEV-9932 provide a default value of the current date for date fields
- Closed
- is blocked by
-
MDEV-10201 Bad results for CREATE TABLE t1 (a INT DEFAULT b, b INT DEFAULT 4)
- Closed
-
MDEV-10207 DEFAULT udf(x) does not return an error when UDF is dropped
- Closed
- is part of
-
MDEV-10137 Providing compatibility to other databases
- Open
- relates to
-
MDEV-6445 UUID column type addition for distributed systems
- Closed
-
MDEV-10351 Prepared statement with parameters in new DEFAULT syntax fails with syntax error upon execution
- Closed
-
MDEV-10352 Server crashes in Field::set_default on CREATE TABLE
- Closed
-
MDEV-10353 New DEFAULT logic does not support use of some suitable functions
- Closed
-
MDEV-10354 Assertion `! is_set()' failed in Diagnostics_area::set_ok_status on CREATE TABLE with invalid default
- Closed
-
MDEV-10355 Weird error message upon CREATE TABLE with DEFAULT: Function or expression 'cache' cannot be used in the ??? clause
- Closed
-
MDEV-11137 TIMESTAMP has 2-level logic for default values
- Open
-
MDEV-14700 ALTER TABLE fails with bogus "BLOB/TEXT column '(null)' can't have a default value"
- Closed
-
MDEV-11136 Orpho error in ER_EXPRESSION_REFERS_TO_UNINIT_FIELD text
- Open