Custom Junction Objects for Many-to-Many Database Relationships

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database systems lack the ability to define custom junction objects, limiting their benefits in online environments and restricting enhanced security and efficient querying capabilities.

Innovation Solution

Mechanisms and methods for defining custom junction objects in an on-demand database service, enabling a many-to-many relationship between arbitrary objects and storing related information, with security criteria and rollup functionality to enhance security and querying efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional database frameworks are used, then system simplicity is maintained, but the ability to define custom junction objects and support many-to-many relationships is lost

Engineering Contradiction:
Improveability to define custom junction objectsVSAvoiddatabase framework complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the database framework into modular components, allowing custom junction objects to be defined as separate, configurable entities. This enables the system to maintain simplicity for standard operations while providing enhanced adaptability for custom many-to-many relationship definitions when needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal junction object framework that can handle both standard and custom many-to-many relationships through a unified interface. This allows the system to provide extended functionality for custom junction objects while maintaining compatibility with conventional database operations, avoiding the need for separate complex subsystems.

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

2Reliability

If custom junction objects are implemented, then enhanced security and querying capabilities are achieved, but system complexity increases

Engineering Contradiction:
Improvesecurity and querying efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces junction objects as intermediary entities that mediate between parent objects in many-to-many relationships. These intermediaries provide a structured layer for implementing security criteria and rollup functionality, isolating the complexity of security and querying enhancements from the core database framework while maintaining reliability improvements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by pre-defining security criteria and rollup functionality templates that can be applied to custom junction objects. This allows security and querying enhancements to be configured in advance through metadata and templates, reducing the complexity of implementing these features for each custom junction object individually.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If traditional database frameworks are used, then ease of operation is maintained, but benefits of custom junction objects such as rollup functionality are void

Engineering Contradiction:
Improverollup functionality and security criteriaVSAvoidease of defining relationships
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements self-service capabilities that allow users to define and configure custom junction objects with rollup functionality and security criteria through intuitive interfaces and automated processes. The system automatically generates the necessary structure and configurations based on user specifications, maintaining ease of operation while providing advanced functionality.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent makes the database schema dynamic by allowing custom junction objects to be defined and modified at runtime without requiring complex schema changes. This enables users to easily adapt the database structure to meet changing business requirements while maintaining operational simplicity through automated schema management and validation.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10949435B2System, method and computer program product for defining custom junction objects in an on-demand database service
Publication Date: 2021.03.16 SALESFORCE INC
  • US10949435B2 patent drawing
  • US10949435B2 patent drawing
  • US10949435B2 patent drawing

AI summary

In accordance with embodiments, there are provided mechanisms and methods for defining custom junction objects in an on-demand database service. These mechanisms and methods for defining custom junction objects in an on-demand database service can enable embodiments to provide for enhanced security and more efficient querying, etc. The ability of embodiments to provide such features may lead to these and other benefits in an on-line environment.