IP Library › Granted Patent US 12,327,092
Granted Patent B2
US 12,327,092 · App. 17/375,563 · Granted Jun 10, 2025

Artificial intelligence (AI) framework to identify object-relational mapping issues in real-time

Inventors: Deepan Kanagaraj (Chennai, IN); Magesh Sripathy (Chennai, IN); Sachin Thakral (Hansi, IN); Vishnuvardhan Rao Regalla (Hyderabad, IN); Prasanna K (Chennai, IN); Suki Ramasamy (Chennai, IN)
Assignee: Bank of America Corporation
G06F8/24G06F16/2282G06F16/288G06F40/226
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,327,092
App. No.
17/375,563
Granted
Jun 10, 2025
Kind
B2
Abstract

An artificial intelligence (AI) model may be trained to identify errors in mapping between relational databases and objects during code compilation. Multiple AI models may be used, with different models being associated with different programming frameworks, thereby making this technique framework agnostic. Errors in mapping between relational databases and objects may be identified based on comparison between object relational mapping (ORM) metadata (e.g., as identified using an AI natural language processing (NLP) model applied to one or more ORM files) and attributes associated with the relational databases.

Claims (60)

1. A system, associated with an integrated development environment (IDE), for validation of object-relational mapping (ORM) used in computer source code files, the system comprising:

a user device configured to provide an IDE, wherein the IDE determines a plurality of source code files, wherein the plurality of source code files comprise one or more ORM files, and wherein the one or more ORM files map relational databases to objects referenced by the source code files; and

an ORM monitoring platform communicatively coupled to the user device, the ORM monitoring platform comprising:

at least one processor; and

memory storing computer-readable instructions that, when executed by the at least one processor, cause the ORM monitoring platform to:

receive a request for compilation of the plurality of source code files;

identify the one or more ORM files among the plurality of source code files;

generate, based on the one or more ORM files and using a natural language processing (NLP) model, ORM metadata;

determine attributes associated with the relational databases;

validate, based on a comparison between the ORM metadata and the attributes associated with the relational databases, the ORM metadata; and

send, to the user device, a validation indication, wherein the user device displays the validation indication within the IDE.

2. The system of claim 1 , wherein the ORM metadata comprises at least one of:

indications of tables;

indications of columns; and

combination thereof.

3. The system of claim 2 , wherein the attributes associated with the relational databases indicate at least one of:

tables included in the relational databases;

columns included in the relational databases; and

combination thereof.

4. The system of claim 3 , wherein sending the validation indication comprises sending an error notification based on determining that the ORM metadata does not match the attributes associated with the relational databases.

5. The system of claim 1 , wherein the determining the attributes associated with the relational databases is based on database catalog information associated with the relational databases.

6. The system of claim 1 , wherein the determining the attributes associated with the relational databases is based on a deployment log associated with the relational databases.

7. The system of claim 1 , wherein the identifying the one or more ORM files comprises determining a programming language associated with the plurality of source code files, wherein the NLP model is based on the determined programming language.

8. A method for validating object-relational mapping (ORM) used in a plurality of source code files submitted via a user device, the method comprising:

receiving, from the user device, a request for compilation of the plurality of source code files;

identifying one or more ORM files among the plurality of source code files, wherein the one or more ORM files map relational databases to objects referenced by the source code files;

generating, based on the one or more ORM files and using a natural language processing (NLP) model, ORM metadata;

determining attributes associated with the relational databases;

validating, based on a comparison between the ORM metadata and the attributes associated with the relational databases, the ORM metadata; and

sending, to the user device, a validation indication, wherein the user device displays the validation indication within an integrated development environment.

9. The method of claim 8 , wherein the ORM metadata comprises at least one of:

indications of tables;

indications of columns; and

combination thereof.

10. The method of claim 9 , wherein the attributes associated with the relational databases indicate at least one of:

tables included in the relational databases;

columns included in the relational databases; and

combination thereof.

11. The method of claim 10 , wherein sending the validation indication comprises sending an error notification based on determining that the ORM metadata does not match the attributes associated with the relational databases.

12. The method of claim 8 , wherein the determining the attributes associated with the relational databases is based on database catalog information associated with the relational databases.

13. The method of claim 8 , wherein the determining the attributes associated with the relational databases is based on a deployment log associated with the relational databases.

14. The method of claim 8 , wherein the identifying the one or more ORM files comprises determining a programming language associated with the plurality of source code files, wherein the NLP model is based on the determined programming language.

15. A non-transitory computer-readable medium storing computer- executable instructions that, when executed by a computer processor, causes a computing platform to:

receive, from a user device, a request for compilation of a plurality of source code files;

identify one or more object-relational mapping (ORM) files among the plurality of source code files, wherein the one or more ORM files map relational databases to objects referenced by the source code files;

generate, based on the one or more ORM files and using a natural language processing (NLP) model, ORM metadata;

determine attributes associated with the relational databases;

validate, based on a comparison between the ORM metadata and the attributes associated with the relational databases, the ORM metadata; and

send, to the user device, a validation indication, wherein the user device displays the validation indication within an integrated development environment.

16. The non-transitory computer-readable medium of claim 15 , wherein the ORM metadata comprises at least one of:

indications of tables;

indications of columns; and

combination thereof.

17. The non-transitory computer-readable medium of claim 16 , wherein the attributes associated with the relational databases indicate at least one of:

tables included in the relational databases;

columns included in the relational databases; and

combination thereof.

18. The non-transitory computer-readable medium of claim 17 , wherein sending the validation indication comprises sending an error notification based on determining that the ORM metadata does not match the attributes associated with the relational databases.

19. The non-transitory computer-readable medium of claim 15 , wherein the determining the attributes associated with the relational databases is based on database catalog information associated with the relational databases.

20. The non-transitory computer-readable medium of claim 15 , wherein the determining the attributes associated with the relational databases is based on a deployment catalog associated with the relational databases.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 14, 2021
From: KANAGARAJ, DEEPAN; SRIPATHY, MAGESH; THAKRAL, SACHIN; REGALLA, VISHNUVARDHAN RAO; K, PRASANNA; RAMASAMY, SUKI
To: BANK OF AMERICA CORPORATION
Reel/Frame 056854/0062 →
Continuity (1)
Related Publication 20230018525A1 · Jan 19, 2023
References Cited (14)
US 6108648A · Lakshmi et al. · 2000 [cited by applicant]
US 7516121B2 · Liu et al. · 2009 [cited by applicant]
US 7647298B2 · Adya et al. · 2010 [cited by applicant]
US 7730065B2 · Fisher et al. · 2010 [cited by applicant]
US 8145685B2 · Thompson et al. · 2012 [cited by applicant]
US 9208211B2 · Surtani et al. · 2015 [cited by applicant]
US 9514115B2 · Chen · 2016 [cited by examiner]
US 10268742B2 · Adya et al. · 2019 [cited by applicant]
US 10809984B2 · Mizrahi · 2020 [cited by examiner]
US 11829735B2 · Kanagaraj · 2023 [cited by examiner]
KR 101411083B1 · 2014 [cited by applicant]
Lakshmi et al., “Selectivity Estimation in Extensible Databases—A Neural Network Approach”, 1998, Proceedings of the 24th VLDB Conference, New York, 1998, pp. 623-627. (Year: 1998). [cited by applicant]
Song et al., “Metadata Invariants: Checking and Inferring Metadata Coding Conventions”, 2012, IEEE, pp. 694-704. (Year: 2012). [cited by applicant]
Bernstein et al., “Incremental Mapping Compilation in an Object-to-Relational Mapping System”, 2013, ACM, pp. 1269-1280. (Year: 2013). [cited by applicant]