Abstract: Disclosed herein are systems and methods for embedding database procedures in data-driven software applications written in a language different from the database-procedure language. For example, in some embodiments, the hosting application may be written in ABAP whereas the database procedure may be written in SQLScript. In various embodiments, the database procedures are encapsulated in specially marked methods of the host application, which, when called at runtime, cause the database procedures to be created in a database catalog and executed on a database server.

Abstract: Disclosed herein are systems and methods facilitating extensions to software applications that access a database, and in particular to applications with embedded database procedures. In various embodiments, an extension anchor embedded in the application as well as one or more extensions implemented as database procedures are encapsulated in specially marked database-procedure methods.

Abstract: Disclosed herein are systems and methods for the hot deployment of database procedures embedded in a host software application. In various example embodiments, the database procedures are encapsulated in specially marked methods of the host application, which, when called at runtime, cause the database procedures, and associated procedure stubs through which the database procedures are called, to be created in a database catalog and executed on the database server. When an embedded database procedure is modified in an application by one user during execution of that application by a second user, compilation of the modified database procedure may result in deletion of the original database procedure and/or associated procedure stub from the database, avoiding inconsistencies between database procedure versions during application execution by the second user.

Abstract: In one embodiment, a method includes defining a parent structure including an extension. A polymorphic structure is defined for the extension. The polymorphic structure is associated with a plurality of client specialization structures, each client specialization being associated with a client in a plurality of clients. During runtime by a computing device, the parent structure is generated with an extension to a client specialization structure associated with one of the plurality of clients where client specialization structures associated with other clients are not visible to the parent structure.

Abstract: Disclosed herein are systems and methods for the hot deployment of database procedures embedded in a host software application. In various example embodiments, the database procedures are encapsulated in specially marked methods of the host application, which, when called at runtime, cause the database procedures, and associated procedure stubs through which the database procedures are called, to be created in a database catalog and executed on the database server. When an embedded database procedure is modified in an application by one user during execution of that application by a second user, compilation of the modified database procedure may result in deletion of the original database procedure and/or associated procedure stub from the database, avoiding inconsistencies between database procedure versions during application execution by the second user.

Abstract: Disclosed herein are systems and methods facilitating extensions to software applications that access a database, and in particular to applications with embedded database procedures. In various embodiments, an extension anchor embedded in the application as well as one or more extensions implemented as database procedures are encapsulated in specially marked database-procedure methods.

Abstract: Disclosed herein are systems and methods for embedding database procedures in data-driven software applications written in a language different from the database-procedure language. For example, in some embodiments, the hosting application may be written in ABAP whereas the database procedure may be written in SQLScript. In various embodiments, the database procedures are encapsulated in specially marked methods of the host application, which, when called at runtime, cause the database procedures to be created in a database catalog and executed on a database server.

Abstract: In one embodiment, a method includes defining a parent structure including an extension. A polymorphic structure is defined for the extension. The polymorphic structure is associated with a plurality of client specialization structures, each client specialization being associated with a client in a plurality of clients. During runtime by a computing device, the parent structure is generated with an extension to a client specialization structure associated with one of the plurality of clients where client specialization structures associated with other clients are not visible to the parent structure.

Abstract: A shared memory technology where shared objects can be used by any of multiple users, applications, or program sessions with programming language support during development and at runtime. The developer can declare shared memory behaviors at design time to cause one or more area classes to be generated for use at runtime. A shared objects memory is managed by the runtime environment. Content is stored at runtime in an area instance of an area class. Class methods to be generated that include methods for attaching and detaching a running session to and from an area instance, and for detaching a session from a change request on an area instance with a commit or a rollback. The runtime environment manages locks for area instances. There are programming language constructs for creating area instances and for creating data objects of arbitrary data type within area instances.