This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 320772 - Error on first Query is removed when a second Query is added
Summary: Error on first Query is removed when a second Query is added
Status: CLOSED FIXED
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-23 16:45 EDT by Navid Mehregani CLA
Modified: 2012-03-05 09:31 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Mehregani CLA 2010-07-23 16:45:53 EDT 
Build Identifier: 

A Query artifact requires a returned entity type.  When an artifact is initially added, user is correctly warned of this.  However, as soon as a second Query is added the error on the first Query artifact goes away!

Reproducible: Always

Steps to Reproduce:
1. Create a new class diagram
2. Create a Query artifact. Notice that the following is correctly logged in Problems view: Undefined returned Entity type referenced in 'Query6'
3. Create a second Query artifact.  Notice the problem in the first Query artifact goes away
4. Create a returned entity for the second Query by adding an Entity artifact and specifying it as a returned type of the second Query.  Now the model builds with no problems even though the first Query still doesn't have a returned entity!
Comment 1 Eric Dillon CLA 2010-08-09 21:58:13 EDT 
Query are seldom used.
Comment 2 Navid Mehregani CLA 2012-03-05 09:31:07 EST 
Fixed.