A virtual table is a type of table whose content is defined by a synapse SQL query. Its content is NOT persisted and any query on a virtual table will run the defined SQL statement. The defining SQL of the virtual table CANNOT contain JOIN clauses on multiple tables.
|The name of this entity. Must be 256 characters or less. Names may only contain: letters, numbers, spaces, underscores, hyphens, periods, plus signs, apostrophes, and parentheses
|The description of this entity. Must be 1000 characters or less.
|The unique immutable ID for this entity. A new ID will be generated for new Entities. Once issued, this ID is guaranteed to never change or be re-issued
|Synapse employs an Optimistic Concurrency Control (OCC) scheme to handle concurrent updates. Since the E-Tag changes every time an entity is updated it is used to detect when a client's current representation of an entity is out-of-date.
|The date this entity was created.
|The date this entity was last modified.
|The ID of the user that created this entity.
|The ID of the user that last modified this entity.
|The ID of the Entity that is the parent of this Entity.
|Indicates which implementation of Entity this object represents. The value is the fully qualified class name, e.g. org.sagebionetworks.repo.model.FileEntity.
|The version number issued to this version on the object.
|The version label for this entity
|The version comment for this entity
|If this is the latest version of the object.
|The columns of a virtual table are dynamic based on the select statement of the definingSQL. This list of columnIds is for read only, and will be ignored for create and update operations.
|When creating or updating a table or view specifies if full text search should be enabled. Note that enabling full text search might slow down the indexing of the table or view.
|The synapse SQL statement that defines the data in the virtual table. The SQL CANNOT contain JOIN/UNION clauses on multiple tables.