Project

General

Profile

Bug #10482

« Previous | Next »

[REGRESSION] DMO temp-table SQL name is no longer deterministic

Added by Constantin Asofiei 11 months ago. Updated 11 months ago.

Status:
WIP
Priority:
High
Assignee:
Octavian Adrian Gavril
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Constantin Asofiei 11 months ago

Since 16131 or earlier, when converting for regression testing a large app, the DMOs are no longer the same - the SQL name for the temp-table is different.

#2 Updated by Alexandru Lungu 11 months ago

  • Priority changed from Normal to High
  • Assignee set to Octavian Adrian Gavril
  • Subject changed from DMO temp-table SQL name is no longer deterministic to [REGRESSION] DMO temp-table SQL name is no longer deterministic

#3 Updated by Octavian Adrian Gavril 11 months ago

  • Status changed from New to WIP

I'm not sure if this is a regression. I've seen that kind of differences many times when converting a large app. The last comparison I did was trunk/16123 vs trunk/16139 and these differences were present. I'm investigating this issue.

Also available in: Atom PDF