Sap Se

Sap Ag

Daniel Hutzel

Stefan A Baeuerle

Timm Falter

Udo Peter Klein

Jan Teichmann

Thomas Gauweiler

Jens Weiler

Frank Brunswig

Di Wu

Joachim Fitzer

Ki Hong Kim

Marcel Hermanns

Steffen Tatzel

Daniel Goldmann

Dirk A Giebel

Lior Schejter

Heiko Steffen

Meinolf Block

Daniel Zoch

Gunther Liebich

Bjoern Mielenhausen

Abhay A Tiple

Malte Wedel

Udo Offermann

Marcel Kassner

Michael Brombach

Jochen Guertler

Steffen Weinstock

Zhi Qiao

Long Zhang

Andreas Gruenhagen

Anton Forstreuter

Andreas Bader

Peter Anselmann

Urlich Bestfleisch

Monika Kaiser

Nili Avitan

Oliver Jaegle

A system, medium, and method to define a database table and view based on a database model using a database language statement, the database language statement including a statement to create the table and a forward-declared JOIN statement that names the table and view, respectively and includes information regarding a relationship between at least two entities of the database.

Enhancements for forward joins expressing relationships

A method for propagating a structure query language (SQL) association can include determining, based at least on a syntax of a SQL create view statement, that a SQL association requires propagation to a SQL view associated with the SQL create view statement. The SQL association can combine data from at least a first data model and a second data model at a database. The SQL view can comprise at least a portion of the combined data. An association information data structure can be generated for storing information corresponding to a definition of the SQL association. The SQL create view statement can be executed based on the association information data structure. Related systems and articles of manufacture, including computer program products, are also disclose.

Propagation of structured query language associations

A database language (e.g. SQL) is extended to define a transient field whose value is derived from data stored in a database. The value of the transient field is calculated by the database engine for consumption as needed by the application layer, for example as part of a particular data model. The value of the transient field may not be materialized as a persistent field in the underlying database table, or may be selectively materialized based upon a heuristic or hint. Certain embodiments may implement the transient field as a basic elaboration on standard SQL utilizing an identifier. Some embodiments may implement the transient field as an entity where SQL has been extended to accommodate concepts of a higher-level Entity Relationship Model (ERM). The use of constants and/or floating values (e.g. a current time) in connection with transient fields, is also disclosed.

SQL extended with transient fields for calculation expressions in enhanced data models

A system includes reception of a configuration set definition file defining the structure of one or more customizing tables of a software application, reception of a configuration data file including data for the one or more customizing tables, and, during activation of the software application in a run-time system, generation of the one or more customizing tables based on the configuration set definition file, generation of a service to access the configuration data file, and population of the one or more customizing tables with data of the configuration data file.

File-based transport of table content

Disclosed are techniques employed alone or in combination, to further enhance a database language and improve conciseness and comprehensiveness of query statements in application code. Embodiments may build upon an initial extension of database language to accommodate concepts of entity-relationship models (ERMs). That initial extension may include entities with structured types, and named associations. One technique modifies SQL to allow the SELECT command to specify element path expressions based upon a relationship (e.g. named associations between ERM elements). Another technique modifies SQL to introduce filter expressions suffixed to associations within path expressions, thus improving adherence to the principle of locality within query statements. Yet another technique allows a shorthand to 'factor out' association path prefixes, thereby avoiding lengthy lists of path expressions in order to read several elements from the same nested structure or a same target entity behind a single association. Other techniques simplifying database querying are also disclosed.

SQL enhancements simplifying database querying

Embodiments extend the relational model and query language to recognize features of tables and higher level entity-relationship models (ERMs). Extension language is implemented in the data design language (DDL) to incorporate tables, entities (and views) having custom-defined/semantic structure, rather than being limited to primitive types (e.g. flat tables as in standard SQL). The extension language includes an indication that a query is to include all active elements for each table extension or entity extension that is active. The extension language can be chained to extend a table or entity that has been extended.

Core data services extensibility for entity-relationship models

A technique is described for generating error buffer that includes errors from both a program and event handlers called by the program. A program in an event-driven environment triggers an event. In response to the triggered event, the program calls event handlers related to the event. The event handlers are executed and error messages generated during the execution are stored in a local error buffer. Upon completion of the event handlers, the local error buffers are returned to the program and the program merges the local error buffers with an error buffer associated with the program.

Local buffers for event handlers

Embodiments extend the relational model and language of standard SQL, to recognize features of higher level entity-relationship models (ERMs). SQL extensions implemented in the data design language (DDL) incorporate Entities (and Views) having custom-defined/semantic structure, rather than being limited to primitive types (e.g. flat tables as in standard SQL). Entities are defined similar to structured types with an underlying persistency, but with a uniquely identifying leading key. In DDL, these entities are combined with associations in the data model. The associations of the extended SQL reflect relationships between entities in the ERM. Associations are specified by adding an element to a source entity, with an association type pointing to a target entity. This may be complemented by providing optional information (e.g., cardinality, keys, filter conditions), up to a complete JOIN condition. In the query language (QL), JOINs may be replaced by the use of simple path expressions.

Database language extended to accommodate entity-relationship models

Embodiments extend the relational model and language of standard SQL, to recognize features of higher level entity-relationship models (ERMs). Annotation language is implemented in the data design language (DDL) to incorporate tables and entities Using DDL, annotations are typed structures of metadata. Annotations may be used for types, entities and elements. In the query language (QL), annotations may be added to the standard QL. A reflection program may use the metadata of the annotation language for reflection on the tables or entities.

Entity-relationship model extensions using annotations

Techniques are described for expressing a constraint in a host language. A constraint can be defined in the host language as an event handler. The event handler can be registered to a built-in event associated with an object of the database that the constraint is intended to validate. When the object triggers the built-in event, the event handler is called to execute the constraint. Exemplary built-in events include onSave (trigger the event when the object is saved), onValidate (trigger the event when an explicit call to validate the object is detected), onInsert (trigger the event when the object is inserted), onUpdate (trigger the event when the object is updated), and onCheckBeforeSave (trigger the event when the object is checked prior to saving).

Data models containing host language embedded constraints

A database language is extended to define constraints on a data model (e.g., entity-relationship model) rather than the concrete database. The constraints can be declarative (e.g., constraints that are defined using expressions of the database language) or programmatic (e.g., constraints that are defined as a stored procedure implemented in a domain specific language). By storing the constraints at a higher level than the database level, the constraints can be performed without changing the persistency of the database. Also disclosed are techniques for handling of constraints on partially loaded entities.

Advanced data models containing declarative and programmatic constraints

Methods and apparatus, including computer program products, are provided for providing a query language based on a model. In one aspect, there is provided a computer-implemented method. The method may include receiving a first query; generating, based on a model including metadata representing a data structure, a second query specific to the data structure stored in a database; and sending the second query to the database. Related apparatus, systems, methods, and articles are also described.

Query language based on business object model

Systems and methods consistent with the invention may include displaying, during debugging of source code having corresponding executable code, a screen including a first section, wherein a variable name included in the source code is displayed in a first format in the first section, receiving a user selection of the variable name, converting, by using a processor, the first format of the variable name to a second format in response to the received selection, wherein the variable name includes a plurality of characters and converting the first format of the variable name to the second format includes converting the characters to uppercase, searching for a corresponding variable name in the executable code, and displaying, on the display device, a second section including the corresponding variable name, wherein the variable name is displayed in a third format in the second section.

Systems and methods for processing source code during debugging operations

Embodiments of the invention relate to computing, and in particular, to a systems and methods for a querying a database. Certain embodiments implement a model-driven database query ('the SADL query') facilitating a design-time tool that allows a developer to create the query based upon existing Business Objects (BOs) and their associations. This SADL query leverages mapping between business-layer entities and database-layer entities, such mapping being derived from association metadata already extant in the business model used to create the Business Objects. In certain embodiments, query views may be based upon associations present within the business layer, rather than upon database-level entities (such as joins or restriction rules) that are typically relied upon in conventional query creation. Embodiments of the present invention may thus align query creation more closely with the structure of the business layer, and may also render query design agnostic relative to the identity of the underlying database.

Growing community of inventors

Walldorf, Germany

Daniel Hutzel