Abstract: Dynamic materialization of a feed is described. A request for a feed is received. A state of the feed is determined. Responsive to determining that the state is the inactive state, causing materialization of the feed in a second non-relational database system with feed items of the feed from the first relational database system, where the second database system is separate from the first database system, and setting the state of the feed to the activating state. Responsive to determining that the state is the active state, causing the request for the feed to be processed from the second non-relational database system.

Abstract: Dynamic materialization of a feed is described. A request for a feed is received. A state of the feed is determined. Responsive to determining that the state is the inactive state, causing materialization of the feed in a second non-relational database system with feed items of the feed from the first relational database system, where the second database system is separate from the first database system, and setting the state of the feed to the activating state. Responsive to determining that the state is the active state, causing the request for the feed to be processed from the second non-relational database system.

Abstract: Dynamic materialization of a feed is described. A request for a feed is received. A state of the feed is determined. Responsive to determining that the state is the inactive state, causing materialization of the feed by populating a materialized feeds table in a second non-relational database system with feed items of the feed from the first relational database system, and setting the state of the feed to the activating state. Responsive to determining that the state is the active state, causing the request for the feed to be processed from the materialized feeds table in the second non-relational database system. Responsive to determining that the state is the disabled state, causing the request for the feed to be processed from the first relational database system, and causing an update of the materialized feeds table in the second non-relational database system to be postponed for a predetermined amount of time.

Abstract: Dynamic materialization of a feed is described. A request for a feed is received. A state of the feed is determined. Responsive to determining that the state is the inactive state, causing materialization of the feed by populating a materialized feeds table in a second non-relational database system with feed items of the feed from the first relational database system, and setting the state of the feed to the activating state. Responsive to determining that the state is the active state, causing the request for the feed to be processed from the materialized feeds table in the second non-relational database system. Responsive to determining that the state is the disabled state, causing the request for the feed to be processed from the first relational database system, and causing an update of the materialized feeds table in the second non-relational database system to be postponed for a predetermined amount of time.

Abstract: Methods and systems for using a scheduler in a data pipeline are disclosed. A plurality of objects in a first layer are created, each representing a respective regularly scheduled task. A plurality of objects in a second layer are created, each representing a respective scheduled instance of a regularly scheduled task. It is determined whether each object in the second layer is ready to execute. For at least one object in the second layer, it is determined if the object has received notifications from any objects on which it depends. For each object that is ready to execute, the regularly scheduled task associated with the object is performed. For each object that is not ready to execute, the object is put to sleep.

Abstract: Disclosed are methods, apparatus, systems, and computer readable storage media for publishing a cross-referenced feed item for access by one or more followers in an online social network. A request to publish a feed item to a feed of a parent entity is received at a computing device, where the parent entity is identified in a database of the online social network. An entity is identified as being cross-referenced with the feed item, where the cross-referenced entity has one or more followers. A request to publish the feed item for access by the one or more followers of the cross-referenced entity is received at the computing device. The feed item is stored in one or more database tables in association with the parent entity and in association with the cross-referenced entity, the feed item capable of being provided in a plurality of information feeds accessible by the one or more followers including the parent entity feed and one or more feeds of the one or more followers.

Abstract: Disclosed are methods, apparatus, systems, and computer readable storage media for interacting with a record via a single user interface. The user interface includes a publisher and an information feed. A user may request to interact with the record from the publisher. Information may be submitted through the publisher to interact with the record to update the record. A feed item may be presented for inclusion in the information feed based on the update. One or more entities may be cross-referenced with the feed item so that the same feed item is provided in the feeds of each of the one or more entities. Identification of the entities to be cross-referenced with the feed item can come from data defined by a user in a payload, data defined by a system administrator, and/or record relationship information in a database system.

Abstract: A system and method that facilitate data access in a software development environment is provided. The system generates strongly typed objects that encapsulate raw, untyped data access logic and groups together like database commands in a common data access component. The system provides a mapping between database types and common language runtime data types including the impedance mismatch of null representations. The system configures data access component(s) that are employed at design-time to facilitate access to data object(s) by application(s) and allows a user of the configured data access component(s) to improve developer productivity and/or reduce the quantity of runtime errors introduced into code. The data access component can be instanced on multiple forms components and/or with the developer's own class(es). Thus, change(s) to a query and/or interface are accomplished within the data access component and be available to the forms components and/or object(s) that utilize the data access component.

Abstract: A system and method that facilitate data access in a software development environment is provided. The system generates strongly typed objects (e.g., TableAdapter(s)) that encapsulate raw, untyped data access logic, for example, via generated wrapped method(s). The system can group together like database commands in a common data access component. For example, the TableAdapter can encapsulate a configured DataAdapter and expose public method(s) for the “Fill” and “Update” methods normally found on the DataAdapter. The system provides a mapping between database types and common language runtime data types including the impedance mismatch of null representations. The system includes a data access configuration component (e.g., configuration wizard) that configures data access component(s) (e.g., TableAdapter(s)). The configured data access component(s) can be employed at design-time to facilitate access to data object(s) (e.g., database(s)) by application(s).