[MDEV-10901] FR: Hidden columns Created: 2016-09-26  Updated: 2016-09-27  Resolved: 2016-09-27

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Anders Karlsson Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-10177 Invisible columns Closed

 Description   

There are 2 instances in SQL where the columns of a table are inferred from the table they are part of, which is SELECT * and INSERT without column names. This Feature Request is to allow certain columns to be "hidden" in those two cases. The idea is that a column with the HIDDEN (possibly we separate the two cases so a HIDDEN_SELECT and HIDDEN_INSERT are two separate attributes). This feature would allow some interesting construct in particular when migrating from other databases or when replicating from them. An example is the ability to retain the Oracle ROWID which would be stored in a separate column with the HIDDEN attribute. If columns are explicitly named in an INSERT or SELECT statement, then they would work as usual, they would only be hidden when not specifically asked for. Another usecase beyond rowid would be to have them as temporary computed columns, for virtual columns then this feature could be used to allow selection of only the computed value (for example order value after VAT has been added).



 Comments   
Comment by Sergei Golubchik [ 2016-09-26 ]

A duplicate of MDEV-10177?

Comment by Anders Karlsson [ 2016-09-26 ]

Yes, I should have checked first. Sorry. But this is the simple case (step 2) of MDEV-10177. Still a useful feature.

Comment by Sergei Golubchik [ 2016-09-27 ]

MDEV-10177 is already implemented (but not pushed yet), so it has your use case covered

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