Abstract: Runtime data for generating visualizations based on a query is stored separate from metadata in memory, thereby allowing for other runtime data for different visualizations based on the same query to reference that metadata without duplicating the metadata in memory. First metadata of first query data received from a server is loaded into a metadata store in memory. First runtime data for a first visualization is loaded in memory separately. The first runtime data uses the first metadata without reloading the first metadata on the one or more primary memory devices. Second runtime data for a second visualization may also use the first metadata of the metadata store such that the first metadata is not reloaded into the memory.

Abstract: Different server engines may be used to process queries from a client application. The different engines may have different capabilities and support different features. A server may only provide system level capabilities such that it will indicate that it is not capable of supporting a particular feature if not all of its engines are capable of supporting that feature. In order to use features actually supported, a client application may override the server's feature support information using a client library. The client application may render user interface dialogs supporting a particular feature based on the feature support information from the server as modified by the client library. The dialog may be used to query the server using the feature indicated as not being supported by the server at a system level.

Abstract: A system includes reception of a user selection of at least two dimensions of a data source, acquisition of data of the data source, the data associating each of a plurality of dimension values of a first dimension of the selected dimensions with one or more of dimension values of a second dimension of the selected dimensions, determination, based on the acquired data, of graph nodes representing dimension values of the first dimension and graph edges connecting the graph nodes and representing dimension values of the second dimension, generation of a graph image comprising the graph nodes and graph edges, and transmission of the graph image to the user.

Abstract: A system includes reception of a user selection of at least two dimensions of a data source, acquisition of data of the data source, the data associating each of a plurality of dimension values of a first dimension of the selected dimensions with one or more of dimension values of a second dimension of the selected dimensions, determination, based on the acquired data, of graph nodes representing dimension values of the first dimension and graph edges connecting the graph nodes and representing dimension values of the second dimension, generation of a graph image comprising the graph nodes and graph edges, and transmission of the graph image to the user.

Abstract: A method for selectively enabling requests includes There is a first list of in-development backend capabilities and a second list of ready-for-release backend capabilities. There is a third list of in-development middleware capabilities and a fourth list of ready-for-release middleware capabilities. There is a fifth list including backend capabilities which are exposed to a user interface by middleware capabilities, the fifth list being an intersection of the second list and the fourth list. There is a sixth list of development capabilities by taking an intersection of the first list and the third list combined with an intersection of the second list and the third list. Input is accepted from the user interface moving selected development capabilities from the sixth list to the fifth list. Requests from the user interface directed to the backend are selectively enabled to allow only requests directed to backend capabilities of the fifth list of capabilities.

Abstract: A method for selectively enabling requests includes There is a first list of in-development backend capabilities and a second list of ready-for-release backend capabilities. There is a third list of in-development middleware capabilities and a fourth list of ready-for-release middleware capabilities. There is a fifth list including backend capabilities which are exposed to a user interface by middleware capabilities, the fifth list being an intersection of the second list and the fourth list. There is a sixth list of development capabilities by taking an intersection of the first list and the third list combined with an intersection of the second list and the third list. Input is accepted from the user interface moving selected development capabilities from the sixth list to the fifth list. Requests from the user interface directed to the backend are selectively enabled to allow only requests directed to backend capabilities of the fifth list of capabilities.

Abstract: A cylinder lock includes a side bar assembly comprising a binding bar and a testing bar and code pins, each comprising a key projection, a code hole, and binding features. Partial rotation of the cylinder causes the binding bar to engage the binding features of the code pins to prevent radial movement of the pins. If the code holes of the code pins are aligned with code points of the testing bar, the testing bar is able to move inwardly with the binding bar and out of the slot so as to permit the cylinder to rotate within the bore. If one or more code holes is not aligned with a code point of the testing bar, the code point will contact the body of the code pin and thereby be prevented from moving radially inwardly out of a locking slot, thus blocking rotation of the cylinder.

Abstract: A cylinder lock includes a side bar assembly comprising a binding bar and a testing bar and code pins, each comprising a key projection, a code hole, and binding features. Partial rotation of the cylinder causes the binding bar to engage the binding features of the code pins to prevent axial movement of the pins. If the code holes of the code pins are aligned with code points of the testing bar, the testing bar is able to move inwardly with the binding bar and out of the slot so as to permit the cylinder to rotate within the bore. If one or more code holes is not aligned with a code point of the testing bar, the code point will contact the body of the code pin and thereby be prevented from moving radially inwardly out of a locking slot, thus blocking rotation of the cylinder.