Relational Schema for LDAP Knowledge Referrals

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current relational database systems lack a mechanism to represent and obtain both directory entry data and knowledge referral data from LDAP systems, making it difficult to efficiently retrieve LDAP entry and referral information.

Innovation Solution

A method and system for relational schema definition and query methodology that represents referrals in a relational schema and automatically modifies queries to retrieve LDAP knowledge referrals, using catalog tables to store searchable LDAP attributes and adding special values to SQL statements to fetch referral entries alongside regular entries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional relational database systems are used to store LDAP directory information, then standard relational storage capabilities are provided, but there is no mechanism to represent and retrieve both directory entry data and knowledge referral data

Engineering Contradiction:

Improvecapability to represent and retrieve LDAP referral informationVSAvoidcomplexity of storage and query mechanism

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a relational schema representation of LDAP referral information by copying the hierarchical DIT structure into relational tables. The referral data is represented as relational records that mirror the LDAP referral structure, enabling standard SQL queries to retrieve referral information alongside directory entry data. This copying approach allows the relational database to handle LDAP-specific concepts without requiring complex custom mechanisms.

Inventive Principle:

Principle #26Copying

2Productivity

If LDAP knowledge referral entries are stored in relational database, then referral information can be retrieved, but automatic modification of queries to include referrals is not performed

Engineering Contradiction:

Improveefficiency of retrieving referral informationVSAvoidautomatic query modification capability

Core Design Contradiction:

ProductivityVSExtent of automation

Solution Approach 1:

The patent introduces an intermediary query modification layer that translates standard LDAP search queries into enhanced SQL queries. This intermediary automatically detects when referral information should be included and modifies the query to join relational tables containing referral data. The intermediary handles the automation of query modification without requiring changes to the underlying relational database structure or the application's query logic.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If separate mechanisms are used for directory entries and referral information, then data representation is possible, but retrieval efficiency is reduced

Engineering Contradiction:

Improveease of retrieving both entries and referralsVSAvoidtime to retrieve referral data

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The patent merges the retrieval of directory entry data and referral information into a single unified query operation. By representing both types of data in the relational schema and using SQL joins, the system retrieves entries and their associated referrals simultaneously in one database operation. This eliminates the need for separate retrieval steps and reduces the time required to obtain complete information.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS7779022B2Efficient retrieval and storage of directory information system knowledge referrals

Publication Date: 2010.08.17 ORACLE INT CORP

AI summary

The method, system and computer program product for efficient retrieval of knowledge referral are disclosed. In one approach, the method, system and computer program product modify a query for retrieving an entry from a directory information system, that is stored in a relational database, to retrieve the entry and a knowledge referral.