A big-data view integration platform generates integration guided user interfaces (GUIs). A first edge node ingests push-based and pull-based data from a plurality of platform services, which include legacy and non-legacy services having incompatible communication protocols. An event-based queue receives from the first edge node a plurality of queue events as indirect push-based data. A second set of queue events includes direct push-based data as received directly from a non-legacy platform service. A conformity component integrates the push-based data, the pull-based data, and the plurality of queue events into integration data having an enhanced integration format. A view integration component generates a plurality of data views from the integration data. A second edge node exposes the plurality of data views via an access services application programming interface (API). A new service execution component accesses the access services API to generate integration GUIs based on the data views.

Various embodiments of the disclosure relate to an electronic device, and a method for operating content using the electronic device, wherein the electronic device comprises: a wireless communication circuit; a touch display; a memory; and a processor operatively connected to the wireless communication circuit, the touch display, and the memory. The processor is configured to: receive tag information on various types of content and update a database, obtain tag information having a specific keyword; control the touch display to display a search result for the various types of content corresponding to the obtained tag information; receive selection of at least one content from among the various types of content; receive action information for the selected at least one content; and perform an action corresponding to the received action information. Thus, it is possible to transmit, to another electronic device, various types of content grouped based on the same tag information by attaching the various types of content to one message.

An Application Programming Interface (API) processes object storage requests in an object storage format that are received from client applications. A mapper maps the object storage formatted requests into database statements and executes the statements within a database management system. Results returned from the statements are mapped by the mapper to object-storage constructs and provided to the API in object storage format. The object storage formatted requests are provided from the API to the client applications to satisfy the original client applications' requests.

A method for incremental update of materialized views and a system for answering queries against relational databases, or object-oriented databases, or graph databases, are provided. The system comprises a Storage Engine subsystem, configured to store original data as well as materialized views and subviews in a dedicated subsystem, and a Diff Engine subsystem configured to translate Natural Algebra representations of a Natural Algebra view definition into derived Natural Algebra expressions. The system further comprises an Optimizer configured to translate derived Natural Algebra expressions into Incremental View Maintenance plans, and a Delta Extractor subsystem configured to extract any transactional changes to the original data or batches of the said changes in a form that can be passed as input to the Incremental View Maintenance plans in order to compute the changes to the materialized views.

A process builds a view of a dataset. The process displays a graphical user interface window, including: a schema display region; a visualization region; and a shelf region that includes multiple shelves. The process detects user input to place a data field icon from the schema display region into the visualization region. Upon ceasing to detect the user input, the process associates the data field icon with a first shelf according to its data type and data types corresponding to other data field icons, if any, previously associated with the shelves, and then places the first data field icon within the first shelf. The method further includes determining a view type based on the data field icon and the association of the data field icon with the first shelf, and generating a graphical representation in the visualization region in accordance with the determined view type.

Systems, methods, and computer-readable media for triggering table entries characterizing workflow-related communications occurring between workflow participants are disclosed. The systems and methods may involve presenting a table via a display, the table containing rows and columns defining cells, the rows and cells being configured to manage respective roles of the workflow participants; presenting on the display at least one active link for enabling workflow participants to join in a video or an audio communication; logging in memory, characteristics of the communication including identities of the workflow participants who joined in the communication; and generating an object associated with the table, the object containing the characteristics of the communication logged in memory.

A big-data view integration platform generates integration guided user interfaces (GUIs). A first edge node ingests push-based and pull-based data from a plurality of platform services, which include legacy and non-legacy services having incompatible communication protocols. An event-based queue receives from the first edge node a plurality of queue events as indirect push-based data. A second set of queue events includes direct push-based data as received directly from a non-legacy platform service. A conformity component integrates the push-based data, the pull-based data, and the plurality of queue events into integration data having an enhanced integration format. A view integration component generates a plurality of data views from the integration data. A second edge node exposes the plurality of data views via an access services application programming interface (API). A new service execution component accesses the access services API to generate integration GUIs based on the data views.

A method for pre-utilizing tables before refresh includes selecting a query for execution in a data analytics application and identifying a table specified by the query, for instance a materialized table. Another operation includes computing an encoding, such as a hash value, for at least one portion of the identified table. Another operation includes comparing the computed encoding to a pre-stored encoding for the at least one portion of the identified table. On the condition that the computed encoding is identical to the pre-stored encoding, the operations include utilizing the identified table in executing the query in lieu of re-materializing the identified table. Otherwise, on the condition that the computed encoding differs from the pre-stored encoding, the operations include re-materializing the identified table before returning the results of the query.

Definitions of material views are automatically generated. In general, Automated MV generation identifies a set of candidates MVs by examining a working set of query blocks. Once the candidates are formed, the candidate MVs are further evaluated to calculate a benefit to the candidate MVs. An improved approach for generating a candidate set of MVs is described herein. The improved approach is referred to as the extended covering subexpression technique (ECSE). Under ECSE, various relationships between join sets other than strict equivalence are used to generate new resultant join sets. Such relationships include subset, intersection, superset, and union, which shall be described in further detail below. In some cases, relationships among resultant join sets and initial join sets are considered to generate new resultant join sets. The final resultant join sets are then used to form a candidate set of MVs.

Some embodiments provide a method of emulating a presentation of at least one system object of a first database, based on multiple system objects of a second database. From a client, the method receives a first query for the first database requesting a presentation of the system object. From a metadata storage, the method identifies a second query for the second database that references the system objects of the second database, and generates the requested presentation of the system object. The method replies to the client with the generated presentation.