Abstract: Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes is stored in one or more database locations not specific to any one attribute in the combined set.

Abstract: Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes.

Abstract: Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes.

Abstract: Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes is stored in one or more database locations not specific to any one attribute in the combined set.

Abstract: An attribute is received for storage. Whether the attribute is searchable or non-searchable in storage is determined. Storing the attribute as a searchable attribute comprises storing the attribute in a database table corresponding to a hierarchical class-based object. Storing the attribute as a non-searchable attribute comprises storing the attribute together with one or more other non-searchable attributes as a set of attributes. The set of attributes is stored in a database location outside the database table corresponding to the hierarchical class-based object, and the database location is accessed before the database table. A unique attribute identifier is associated with the attribute to distinguish between a name of the attribute and a name of one of the one or more other non-searchable attributes in the event that the name of the attribute and the name of the one of the one or more other non-searchable attributes are assigned the same name.

Abstract: Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes is stored in one or more database locations not specific to any one attribute in the combined set.

Abstract: An attribute of a hierarchical class-based object is received. The attribute in a database is stored both in a first location in a first table at a first level of a hierarchy of database tables which table hierarchy is based at least in part on a class hierarchy associated with the hierarchical class-based object and in a second location in a second table at a second level of the table hierarchy which second level is higher than the first level.

Abstract: Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes.

Abstract: An attribute is received for storage. Whether the attribute is searchable or non-searchable in storage is determined. Storing the attribute as a searchable attribute comprises storing the attribute in a database table corresponding to a hierarchical class-based object. Storing the attribute as a non-searchable attribute comprises storing the attribute together with one or more other non-searchable attributes as a set of attributes. The set of attributes is stored in a database location outside the database table corresponding to the hierarchical class-based object, and the database location is accessed before the database table. A unique attribute identifier is associated with the attribute to distinguish between a name of the attribute and a name of one of the one or more other non-searchable attributes in the event that the name of the attribute and the name of the one of the one or more other non-searchable attributes are assigned the same name.

Abstract: Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes.

Abstract: An attribute of a hierarchical class-based object is received. The attribute in a database is stored both in a first location in a first table at a first level of a hierarchy of database tables which table hierarchy is based at least in part on a class hierarchy associated with the hierarchical class-based object and in a second location in a second table at a second level of the table hierarchy which second level is higher than the first level.

Abstract: Storing data is disclosed. An attribute to be combined with one or more other attributes is received for storage in a database as a set of attributes. A unique attribute identifier is associated with the attribute. The identifier is usable to distinguish between two attributes in the event that the two attributes have the same name.

Abstract: A dynamic, intelligent user interface for an on-line, virtual application whereby user input customizes the subsequent display of application data and queries presented to the user/applicant. The present invention includes a facility for intelligent editing, data state presentation, and error flagging and correction. In one embodiment of the present invention, the intelligent user interface is implemented as part of a series of dynamically generated web pages (a form set) presented to a user of an ecommerce Internet web site. This presentation is in the form of a collection of tabbed panes of data, the selected pane being displayed on a web page, wherein each pane contains one or more pages of data and queries.

Abstract: An air bag (20) is disclosed having separable fabric layers (40, 42) that are locally integrally woven together using warp threads (82) and weft threads (80). One or more integrally woven tethers (70, 70a) extend between the fabric layers at selected locations. Each tether is formed of a plurality of threads (72, 72a). The threads (72, 72a) can be either additional threads, different from the warp or weft threads, additional warp threads, additional weft threads or any combination thereof.