Abstract: The invention relates to a method for assembling a head-up display (1), comprising the following steps: —attaching a first, resilient compression element (18) to a first edge region (16) of a rear face (14) of the first mirror (13) and attaching a second, resilient compression element (19) to a second edge region (17) of the rear face (14) of the first mirror (13); —introducing the first mirror (13) into a cover module (3) of a housing (2) of the head-up display (1) and adjusting a pre-assembly position of the first mirror (13) in the cover module (3), in which position the compression elements (18, 19) abut support surfaces (27, 28) of the cover module (3); —attaching a base module (6) to the cover module (3), wherein, during the connection process, a front face (15) of the first mirror (13) is contacted by contact elements (23, 24) of the base module (6) and the first mirror (13) is pressed into a final assembly position.

Abstract: A head-up display apparatus for a motor vehicle is disclosed. The head-up display includes a housing part in which an image creation unit of the display apparatus is arranged, and an illumination device, by means of which light is applied to the image creation unit. The image creation unit is configured to provide an image which is projectable onto a light transmissive projection surface. A holding device is secured to the housing part in the region of the illumination device. The image creation unit is retained on the holding device.

Abstract: A head-up display device for a motor vehicle is disclosed. The device includes a housing part in which an image-generating unit of the display device is arranged. The image-generating unit is configured to project an image onto a light-permeable projection surface. The image-generating unit includes a cover element which is connected to the housing part and covers regions of the housing part with respect to the surroundings of the display device. The cover element includes a peg element which is inserted into a corresponding receptacle formed in the housing part. The peg element is expanded with a spreading piece inserted into the peg element. The peg element is fixed in the receptacle as a result of the expansion.

Abstract: The claims are amended to remove multiple dependencies, remove references to the drawings, and to otherwise conform with U.S. practice. No new matter is added. In view of the above amendment, applicant believes the pending application is in condition for favorable examination on the merits. Applicant believes no fee is due with this response. However, if a fee is due, please charge our Deposit Account No. 50-0591, under Order No. 17275-445001 from which the undersigned is authorized to draw. Dated: Sep. 29, 2023 Respectfully submitted, By /Seema M. Mehta/ Seema M. Mehta Registration No.

Abstract: A container group is created using a database deployment infrastructure (DI) administrator (HA). API privileges for the container group are granted, using the HA, to a container group administrator (GA). API privileges for a container created in the container group using the GA are granted, using the GA, to a container administrator (CA). API privileges for the container are granted, using the CA, to a container developer (CD). Schema privileges for the container are granted, using the CA, to a container consumer (CC). API privileges for the container group are revoked, using the HA, from the GA. The container group is dropped using the HA.

Abstract: Systems and methods are disclosed for connection multiplexing in a parallel processing environment. An example method includes requesting, responsive to a request to perform multiple database operations in a single transaction, a connection identifier for a physical connection to the database, providing the connection identifier to each of a plurality of workers, and performing the multiple database operations using the plurality of workers. Each worker may obtain a work item from a work queue, initiate a database request for the work item, and provide the database request to a database server. The database request represents one of the multiple database operations and includes the connection identifier. The database server may determine that the connection identifier corresponds to the physical connection, add the request to a connection queue associated with the physical connection, and execute requests from the connection queue against the database via the physical connection.

Abstract: Parameter-based deployment control for database objects is provided, in which processes for deploying database artifacts into a database as database objects are implemented. Many different techniques may be used in executing such deployment processes, including whether and how to combine various deployment-related jobs, identify/record/assess/correct potential errors, govern or instruct artifact conversion operations, or generally manage available resources with respect to executing the deployment(s) efficiently. By providing for selectable parameter values that are executed in an efficient, e.g., hierarchical, manner, deployment procedures may be implemented in a highly efficient and customizable manner.

Abstract: A computer-implemented method for exporting a database container from a database includes exporting database container metadata including artifact definitions in the metadata along with the actual metadata content to a database management system, exporting the database container including the database objects deployed therein to the database management system. The exporting of the database container includes exporting dependencies and structures of the database objects deployed therein, but not the actual content of the database objects. In some instances, however, exporting of the database container can include exporting the actual content of the database objects in response to user request. The method further includes packing the exported database container metadata and the exported database container in an archive. The data in the archive can be unpacked in substantially reverse order to import the database container into another database.

Abstract: A container group is created using a database deployment infrastructure (DI) administrator (HA). API privileges for the container group are granted, using the HA, to a container group administrator (GA). API privileges for a container created in the container group using the GA are granted, using the GA, to a container administrator (CA). API privileges for the container are granted, using the CA, to a container developer (CD). Schema privileges for the container are granted, using the CA, to a container consumer (CC). API privileges for the container group are revoked, using the HA, from the GA. The container group is dropped using the HA.

Abstract: Systems and methods are disclosed for automatically detecting a connection status in an asynchronous processing request. An example method includes obtaining, at a processing client and responsive to a first request from a requesting client to perform a plurality of database operations in a single transaction, a connection identifier for a connection to a database on a database server, the connection to be used to execute the plurality database operations and storing the connection identifier in a row of a status table. In some implementations the existence of the row indicates the status of the connection is active. In some implementations the row includes a flag indicating the status. The method also includes providing the connection identifier to the requesting client, receiving a second request from the requesting client, the second request being for a status of the connection, determining the status using the status table.

Abstract: A computer-implemented method for deploying a new artifact file in a database. The new artifact file provides specifications for one or more new run-time database objects to be created in the database by processing of the new artifact file by artifact-type specific conversion engines. The method includes assigning ownership of the one or more new run-time database objects to be created in the database to the new artifact file, and, when an existing database object in the database provided by another artifact file corresponds to a new run-time database object specified in the new artifact file, assigning ownership of the existing database object in the database to the new artifact file being deployed.

Abstract: A container group is created using a database deployment infrastructure (DI) administrator (HA). API privileges for the container group are granted, using the HA, to a container group administrator (GA). API privileges for a container created in the container group using the GA are granted, using the GA, to a container administrator (CA). API privileges for the container are granted, using the CA, to a container developer (CD). Schema privileges for the container are granted, using the CA, to a container consumer (CC). API privileges for the container group are revoked, using the HA, from the GA. The container group is dropped using the HA.

Abstract: A dependency graph is generated for database files. An unvisited node of the dependency graph is selected and a breadth-first-search performed starting from the selected unvisited node. Results of the breadth-first-search is defined as a group. A group assignment for the database files is returned.

Abstract: Systems and methods are disclosed for connection multiplexing in a parallel processing environment. An example method includes requesting, responsive to a request to perform multiple database operations in a single transaction, a connection identifier for a physical connection to the database, providing the connection identifier to each of a plurality of workers, and performing the multiple database operations using the plurality of workers. Each worker may obtain a work item from a work queue, initiate a database request for the work item, and provide the database request to a database server. The database request represents one of the multiple database operations and includes the connection identifier. The database server may determine that the connection identifier corresponds to the physical connection, add the request to a connection queue associated with the physical connection, and execute requests from the connection queue against the database via the physical connection.

Abstract: Systems and methods are disclosed for connection multiplexing in a parallel processing environment. An example method includes requesting, responsive to a request to perform multiple database operations in a single transaction, a connection identifier for a physical connection to the database, providing the connection identifier to each of a plurality of workers, and performing the multiple database operations using the plurality of workers. Each worker may obtain a work item from a work queue, initiate a database request for the work item, and provide the database request to a database server. The database request represents one of the multiple database operations and includes the connection identifier. The database server may determine that the connection identifier corresponds to the physical connection, add the request to a connection queue associated with the physical connection, and execute requests from the connection queue against the database via the physical connection.

Abstract: Embodiments map from a database environment, dependencies between files created at designtime and corresponding runtime data objects defined by deployment of those files. A dependency table is populated with dependency information (e.g., origin, target, dependency type) extracted during deployment. That dependency information may be searched according to user-specified parameters (e.g., a file provides an object; an object requires a file), to allow rapid correlation between designtime file(s) and related runtime data object(s). Embodiments are particularly useful in visualizing complex (e.g., one-to-many; many-to-one) file-object dependencies characteristic of modern database environments. Queries posed to the dependency table may further seek intra-designtime dependency information (e.g., one file depends upon another file; one file impacts another file), and/or intra-runtime dependency information (e.g., table objects referenced by view objects; view objects referenced by procedure objects).

Abstract: Whether database objects corresponding to an artifact to deploy already exists in a database is determined. Depending artifacts are calculated using a prior-generated dependency graph. Whether any database objects corresponding to the calculated depending artifacts need to be redeployed are determined. Whether a build plugin corresponding to the database objects needing to be redeployed supports a redeployment option is determined. The artifacts are processed according to an execution graph.

Abstract: A database includes a run-time database container, which provides an isolated computing environment for a database object deployed therein. The database further includes a public synonym object outside the run-time database container in the database. The public synonym object is associated with the database object deployed inside the run-time database container and provides external access to the database object deployed inside the run-time database container independent of the location of the run-time database container.

Abstract: An external database schema permitted to be accessed from a container using a database synonym is determined. A logical schema representing the external database schema is defined. A synonym for the container is defined using the logical schema and an object associated with the external database schema. The logical schema and synonym is deployed to the container using a logical schema plugin. The container is configured to disable the logical schema plugin and to only allow references to the defined logical schemas.

Abstract: An import configuration section of a file is identified, where the import configuration identifies a database table. Key specifications of the database table are reserved based on the import configuration. A first and a second Boolean flag parameter associated with the database table is identified. A determination is made that i) a value of the first Boolean flag indicates importing of entries from the file into the database table is allowed, and that ii) a value of the second Boolean flag indicates removal of entries of the database table is allowed. In response to the determining entries are removed from the database table corresponding to the key specifications, and entries are imported from the file into the database table corresponding to the key specifications.