Project

General

Profile

Bug #3243

possible mismatch in runtime sequence definition and retrieval

Added by Eric Faulhaber over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Low
Assignee:
Ovidiu Maxiniuc
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version:

History

#1 Updated by Eric Faulhaber over 7 years ago

I'm not sure if this is a bug or not, but it warrants further investigation.

I recently noticed SequenceManager.addSequenceDefinition stores sequence objects using a schema parameter as a map key. However, SequenceManager.getSequence specifies an ldbName parameter as a key when doing the lookup in the same map. I have not traced the call hierarchy for each of these methods back to determine the origin of each of these keys, but this mismatch in parameter names looks suspicious, and could represent a latent bug.

In many cases, schema and logical database name are the same in practice, but they could easily differ. We need to make sure the data being passed in for each of these methods is canonical, so that we don't have unexpected mismatches which result in a failure to find a legitimate sequence at runtime.

Also available in: Atom PDF