[MDEV-10178] correct nullability for generated columns Created: 2016-06-05  Updated: 2017-01-26

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Sergei Golubchik Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-371 Unique indexes for blobs Closed

 Description   

Currently all generated columns are created nullable. Because we don't know whether an expression may be NULL or not until we create an item tree and fix_field it. And this only t happens after the .frm is written.

A way to workaround it is to create all generated fields nullable, as now. But after the .frm is opened and fields are fixes — check maybe_null property of all generated columns and mark them not nullable, as appropriate (set null_ptr=0, etc). By doing that we'll lose one bit in the null bitmap per generated not nullable field.


Generated at Thu Feb 08 07:40:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.