Native SAP HANA artifacts
Using a database object CDS did not generate from the model, an existing table, a view with parameters, a table function, a calculation view or a table in another HDI container, and shipping the design-time files CDS cannot express, an index, a synonym, a native clause, in the same deployment. Distinct from database connectorsDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to schema evolution.SAP and community, narrow by design, which is which database the model runs on, and from schema evolutionSchema evolutionGetting a model change into a database that already holds data, in every tenant, without losing any of it. Generating the initial schema and migrating one that already holds data are often treated as the same step.SAP and community, narrow by design, which is getting a model change into data that already exists.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
No SAP artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Artifacts
Details
Coverage
For your agent
- Ref
capability:hana-native-artifacts- JSON
- /capabilities/hana-native-artifacts.json
- MCP
- Connecting an agent