[CI] NetApp Cloud Insights Custom SQL Queries are Like MySQL Views

on

If you're working out how to integrate your applications with NetApp Cloud Insights DataWarehouse, and you're coming from the NetApp OnCommand Insights DataWarehouse world, where you had direct MySQL access to the OCI DWH. You will have come across the Cloud Insights Custom SQL Queries.

The important thing to remember is that Cloud Insights Custom SQL Queries are like views in MySQL. So all the restrictions that apply to views are valid.

The key one I've found is that we cannot use parameters in views. We had some MySQL queries that used parameters. And Splunk was integrating with the OCI DWH using one of these SQL queries. When we were tried to get these same queries working as a CI Custom SQL query, that's when we learn about the restrictions.

See: https://dev.mysql.com/doc/refman/8.0/en/create-view.html

A view definition is subject to the following restrictions:

  • The SELECT statement cannot refer to system variables or user-defined variables.

  • Within a stored program, the SELECT statement cannot refer to program parameters or local variables.

  • The SELECT statement cannot refer to prepared statement parameters.

  • Any table or view referred to in the definition must exist. If, after the view has been created, a table or view that the definition refers to is dropped, use of the view results in an error. To check a view definition for problems of this kind, use the CHECK TABLE statement.

  • The definition cannot refer to a TEMPORARY table, and you cannot create a TEMPORARY view.

  • You cannot associate a trigger with a view.

  • Aliases for column names in the SELECT statement are checked against the maximum column length of 64 characters (not the maximum alias length of 256 characters).

Comments

Post a Comment