Reference documentation and code samples for the Data Analytics API with Gemini V1BETA API class Google::Cloud::GeminiDataAnalytics::V1beta::DatabaseTableReference.
Message representing a table including its schema.
Inherits
- Object
Extended By
- Google::Protobuf::MessageExts::ClassMethods
Includes
- Google::Protobuf::MessageExts
Methods
#schema
def schema() -> ::Google::Cloud::GeminiDataAnalytics::V1beta::Schema- (::Google::Cloud::GeminiDataAnalytics::V1beta::Schema) — Optional. The schema of the table.
#schema=
def schema=(value) -> ::Google::Cloud::GeminiDataAnalytics::V1beta::Schema- value (::Google::Cloud::GeminiDataAnalytics::V1beta::Schema) — Optional. The schema of the table.
- (::Google::Cloud::GeminiDataAnalytics::V1beta::Schema) — Optional. The schema of the table.
#table_id
def table_id() -> ::String-
(::String) — Required. The name of the table as defined in the database.
Note: The precise rules for table naming, including valid characters, length limits, and case sensitivity, are determined by the specific database system.
Requirements:
- Exact Match: The provided name must be identical to the name stored in the database.
- Case Sensitivity: Respect the case sensitivity rules of the specific database system and how the table was created. For example, "Orders" and "orders" may be distinct table names.
- Special Characters/Keywords: If the table name includes spaces, special characters, or is a database reserved keyword, provide the literal name as it is stored. Do not add any database-specific identifier quoting characters (e.g., ", `, []).
Examples:
- Simple name: "orders", "UserActivity"
- Case sensitive: "MyTable"
- Name with spaces: "Order Details"
- Name with other special characters: "user/data", "order-items"
- Name that is a keyword: "Group", "Order"
Permissions: The caller's credentials must have the necessary database permissions to access the table's schema and data.
#table_id=
def table_id=(value) -> ::String-
value (::String) — Required. The name of the table as defined in the database.
Note: The precise rules for table naming, including valid characters, length limits, and case sensitivity, are determined by the specific database system.
Requirements:
- Exact Match: The provided name must be identical to the name stored in the database.
- Case Sensitivity: Respect the case sensitivity rules of the specific database system and how the table was created. For example, "Orders" and "orders" may be distinct table names.
- Special Characters/Keywords: If the table name includes spaces, special characters, or is a database reserved keyword, provide the literal name as it is stored. Do not add any database-specific identifier quoting characters (e.g., ", `, []).
Examples:
- Simple name: "orders", "UserActivity"
- Case sensitive: "MyTable"
- Name with spaces: "Order Details"
- Name with other special characters: "user/data", "order-items"
- Name that is a keyword: "Group", "Order"
Permissions: The caller's credentials must have the necessary database permissions to access the table's schema and data.
-
(::String) — Required. The name of the table as defined in the database.
Note: The precise rules for table naming, including valid characters, length limits, and case sensitivity, are determined by the specific database system.
Requirements:
- Exact Match: The provided name must be identical to the name stored in the database.
- Case Sensitivity: Respect the case sensitivity rules of the specific database system and how the table was created. For example, "Orders" and "orders" may be distinct table names.
- Special Characters/Keywords: If the table name includes spaces, special characters, or is a database reserved keyword, provide the literal name as it is stored. Do not add any database-specific identifier quoting characters (e.g., ", `, []).
Examples:
- Simple name: "orders", "UserActivity"
- Case sensitive: "MyTable"
- Name with spaces: "Order Details"
- Name with other special characters: "user/data", "order-items"
- Name that is a keyword: "Group", "Order"
Permissions: The caller's credentials must have the necessary database permissions to access the table's schema and data.