Package dev.frostlake.system

Class UnmodeledSystemViews

java.lang.Object
dev.frostlake.system.UnmodeledSystemViews
public class UnmodeledSystemViews extends Object
The INFORMATION_SCHEMA views for objects this engine does not model — semantic views, native apps, Cortex services, backups and snapshots, replication, sharing, container services, and the rest. Each is exposed with its FULL live column shape (measured column for column on a real account) and no rows, because that is exactly what a real account returns for a deployment that uses none of those features.

Presence matters even when a view is always empty: a tool that introspects the catalog — a migration framework listing constraints, a client enumerating file formats — issues the query unconditionally, and answering "table does not exist" where a real account answers zero rows is the same class of fidelity bug as returning wrong rows. INDEXES / INDEX_COLUMNS appear here for that reason too: reporting no indexes is accurate for an engine that deliberately has none.

A view listed here graduates out of this class the moment the engine models its objects — see SystemViews for the populated ones.

  • Constructor Summary

    Constructors
    Constructor
    Description
    UnmodeledSystemViews()
     

  • Method Summary

    Modifier and Type
    Method
    Description
    ResultSet
    query(String viewName)
    The named INFORMATION_SCHEMA view with its live column shape and no rows, or null when this class does not define it (the caller then reports the object as non-existent, as live does for a name that is not an INFORMATION_SCHEMA view at all).

    Methods inherited from class java.lang.Object

    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

  • Constructor Details

    • UnmodeledSystemViews

      public UnmodeledSystemViews()

  • Method Details

    • query

      public ResultSet query(String viewName)
      The named INFORMATION_SCHEMA view with its live column shape and no rows, or null when this class does not define it (the caller then reports the object as non-existent, as live does for a name that is not an INFORMATION_SCHEMA view at all).