View Issue Details

IDProjectCategoryView StatusLast Update
0001203Database Workbench v5Firebird Modulepublic2018-02-15 14:49
ReporterMichał Ziemski Assigned ToMartijn Tonies  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
OSWIndowsOS Version7 
Product Version5.0.10 
Summary0001203: Plan analysis fails on specific plans
DescriptionPlan analysis fails for some plans.
If the system fail to recognize the plan it should gracefully print the recieved plan rather than interrupting work with error messages.
Additional InformationExample plan:
PLAN JOIN (T T WM XX_MS INDEX (MIESTROSOBYOID), T T WM XX_M INDEX (MIEID))
PLAN JOIN (T T WM XX_O INDEX (OSOBYID), T T WM XX_PKW INDEX (PLANKONTWMPLANKONTKID))
PLAN SORT (JOIN (SORT (JOIN (JOIN (JOIN (T T WM WM NATURAL, T T L INDEX (TICKETSYS, TICKETSYS)), SORT (JOIN (T T T TL INDEX (TICKETLABELSI), T T T T INDEX (TICKETID)))), T T TL INDEX (TICKETLABELSTICKETTID)))
PLAN (T T L NATURAL), L INDEX (TICKETLABELID)))
TagsNo tags attached.

Relationships

related to 0001211 closedMartijn Tonies IB/Fb; Failure to analyze plan shouldn't interrupt work 
related to 0001240 closedMartijn Tonies TPlanParser.ParsePlanItem: Unrecognized PLAN syntax -- "NATURAL", "INDEX" or "ORDER" not found after alias: RDB$PRIMARY38))))) 

Activities

Martijn Tonies

2015-04-08 10:11

administrator   ~0000374

The plan is displayed in the bottom part of the window, but this could be streamlined due to the error messages, I agree.

Martijn Tonies

2018-02-15 14:49

administrator   ~0000454

0001487

Issue History

Date Modified Username Field Change
2015-04-07 14:54 Michał Ziemski New Issue
2015-04-08 10:11 Martijn Tonies Note Added: 0000374
2015-04-08 10:11 Martijn Tonies Assigned To => Martijn Tonies
2015-04-08 10:11 Martijn Tonies Status new => acknowledged
2015-04-13 14:19 Martijn Tonies Status acknowledged => assigned
2015-04-14 15:09 Martijn Tonies Summary Plan analysis fails => Plan analysis fails on specific plans
2015-04-14 15:10 Martijn Tonies Relationship added related to 0001211
2015-06-09 16:54 Martijn Tonies Relationship added related to 0001240
2018-02-15 14:49 Martijn Tonies Note Added: 0000454
2018-02-15 14:49 Martijn Tonies Status assigned => closed
2018-02-15 14:49 Martijn Tonies Resolution open => duplicate