Database Object Multiplication via Bucket Structure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database systems generate multiple nearly identical objects to account for variations in a subset of attributes, leading to a proliferation of objects and inefficient querying, as each variation results in a separate object, even when other attributes remain the same.

Innovation Solution

The system creates a 'bucket' that associates an object with a multiplier term containing variations of attributes, allowing sub-objects to reference the object and its attribute variations, thereby reducing object proliferation by storing multiple variations within a single bucket instead of separate objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If multiple separate objects are created to account for variations in attributes, then each variation can be represented accurately, but the number of objects proliferates and query efficiency deteriorates

Engineering Contradiction:
Improveattribute variation representationVSAvoidquery efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent merges multiple separate objects that represent variations of the same base object into a single bucket. Instead of creating separate objects for each attribute variation (e.g., different suppliers, sizes, colors), the system consolidates them into one bucket structure that contains references to all variations, thereby reducing the total number of objects while maintaining accurate representation of each variation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The bucket structure serves multiple functions simultaneously: it represents the base object, stores references to all attribute variations, enables efficient querying by returning the entire bucket with its variations, and maintains relationships between the base object and its variations. This multi-functional design eliminates the need for separate objects for each variation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If multiple separate objects are created for each attribute variation, then detailed information about each variation is stored, but device complexity increases

Engineering Contradiction:
Improveattribute variation informationVSAvoidobject structure complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a nested structure where the bucket contains the base object and nested within it are references to multiple sub-objects representing attribute variations. This nesting approach allows detailed information about each variation to be stored while organizing it in a hierarchical structure that reduces overall complexity compared to having flat separate objects for each variation.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The bucket acts as an intermediary structure between the base object and its variations. Instead of directly creating separate top-level objects for each variation, the bucket serves as a mediating container that holds references to all variations, simplifying the object structure while preserving detailed information about each variation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If separate objects are created for each variation, then each object can be accessed independently, but the number of database entries increases

Engineering Contradiction:
Improveobject accessVSAvoidnumber of database entries
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent combines multiple database entries representing variations into a single bucket entry. Instead of having separate rows in the database for each variation (e.g., separate entries for different suppliers or sizes), the system creates one bucket entry that contains references to all variations, thereby reducing the total number of database entries while maintaining the ability to access individual variations through the bucket structure.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10909184B2Multiplication of database objects
Publication Date: 2021.02.02 SAP SE
  • US10909184B2 patent drawing
  • US10909184B2 patent drawing
  • US10909184B2 patent drawing

AI summary

A method for multiplying an object in a database may include receiving, from a client, an indication that an object is associated with a first variable attribute having a first variation and a second variation. A bucket may be created in response to the indication. The bucket may include the object, a first sub-object having a first reference to the first variation of the first variable attribute, and a second sub-object having a second reference to the second variation of the first variable attribute. The bucket may be created instead of a first object having the first variation of the first variable attribute and a second object having the second variation of the first variable attribute. The bucket stored in the database may be accessed in response to a query from the client accessing the object. Related systems and articles of manufacture including computer program products are also provided.