Project

General

Profile

Bug #10482

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

Added by Constantin Asofiei about 1 year ago. Updated 1 day ago.

Status:
Closed
Priority:
High
Target version:
-
Start date:
Due date:
% Done:

100%

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

History

#1 Updated by Constantin Asofiei about 1 year 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 about 1 year ago

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

#3 Updated by Octavian Adrian Gavril about 1 year 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.

#4 Updated by Octavian Adrian Gavril 1 day ago

Constantin, is this still reproducible?

#5 Updated by Constantin Asofiei 1 day ago

Octavian Adrian Gavril wrote:

Constantin, is this still reproducible?

If the conversion is stable (src/ is the same across two runs with trunk), then we are OK.

#6 Updated by Octavian Adrian Gavril 1 day ago

Constantin Asofiei wrote:

Octavian Adrian Gavril wrote:

Constantin, is this still reproducible?

If the conversion is stable (src/ is the same across two runs with trunk), then we are OK.

I believe that's the case for the latest revision of trunk, so this task can be rejected.

#7 Updated by Constantin Asofiei 1 day ago

  • version_resolved set to trunk 16764
  • Status changed from WIP to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF