missed CREATE COLUMN VIEW

[kulliax]

Hi,

While reading the documentation, I came across CREATE COLUMN VIEW, eg here: https://help.sap.com/docs/SAP_HANA_PLATFORM/e8e6c8142e60469bb401de5fdb6f7c00/63efa79c963d4243ad2a894e2b5bd10c.html

I can't find anything about this in the docs:

sap-hana-cloud-hana-database/docs/sql-ref/010-SQL-Reference/012-SQL-Statements/create-view-statement-data-definition-20d5fa9.md

Line 14 in 9a536be

CREATE [ OR REPLACE ] VIEW <view_name> [ COMMENT <string_literal> ]

[sap-doc-bot]

Thank you for your valuable feedback contribution, @kulliax! So that we can recognize your contribution in the SAP Community, please check your SAP Community user ID (this is a number) in your personal settings page and share it with us in a reply to this comment. Make sure you just include the number in the reply.

Your user ID is displayed as follows:

Change display name for User ID N

where N is your user ID. For example, 53 is the user ID of the user 'qmacro'.

Please note that we are currently refactoring our profile and badge system on the SAP Community, and will start assigning badges again when that's complete.

[aptk001]

Hi, thanks for pointing this out. CREATE COLUMN VIEW is a separate statement related to calculation views, but is missing from the documentation. This will be added back in the next time we republish.

[kulliax]

Hi @aptk001

can you give an approximate time frame for a new publication?

SCN: 14806

[aptk001]

There should be a new publication later this month.

An update on this particular issue though, these statements were not included in the SQL reference as they aren't meant to be run directly. Creating calculation views should instead be done using your tool of choice (for example, the instructions are here for Web IDE: https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-modeling-guide-for-sap-web-ide-full-stack/create-graphical-calculation-views).

The examples that currently include steps with running CREATE CALCULATION SCENARIO and CREATE COLUMN VIEW directly need to be updated to reflect this, so I'll pass this feedback on to the relevant teams to update. Thanks again for bringing this up.