Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360029

Summary:

No Default Select Statement Generated for SQL OPEN statement

Product:

z_Archived

Reporter:

Paul Hoffman <hoffmanp>

Component:

EDT

Assignee:

Project Inbox <edt.mofmodel-inbox>

Status:

CLOSED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

chenzhh, jspadea, jvincens

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Test case	none
Supporting library for loading db / table	none

Description Paul Hoffman

2011-10-05 16:02:17 EDT

Created attachment 204630 [details]
Test case

No Default Select Statement Generated for SQL OPEN statement.

See attached test case.

Comment 1 Paul Hoffman

2011-10-05 16:03:12 EDT

Created attachment 204631 [details]
Supporting library for loading db / table

Comment 2 Joseph Vincens

2011-10-13 17:09:34 EDT

Paul this is an IR problem.
The SqlOpenStatementImpl.getSqlString() should use the same code as SqlGetByKeyStatementImpl.getSqlString() when the FOR clause is an Entity.
The default SQL should be SELECT .... FROM
it will have no WHERE clause.

Comment 3 Joseph Vincens

2011-10-13 17:44:14 EDT

also in the case where there is a FOR getResultSet() is returning the FOR record not the ResultSet

Comment 4 Joseph Vincens

2011-10-14 12:00:50 EDT

fixed

Comment 5 Paul Hoffman

2011-10-17 14:51:06 EDT

Verified, closed.

Comment 6 Paul Hoffman

2011-10-24 12:23:54 EDT

Verified and closed.

For future comment, it would be helpful if statement options were expanded to say this is an open for update and if the generated default statement could take into account the key fields for the table.

Comment 7 Paul Hoffman

2011-10-24 12:24:16 EDT

See previous comment.