Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357838 - SQL log should also include info on where it comes from (which Attribute / Basequery)
Summary: SQL log should also include info on where it comes from (which Attribute / Ba...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 454792
  Show dependency tree
 
Reported: 2011-09-15 12:50 EDT by Martin Marinschek CLA
Modified: 2022-06-09 10:10 EDT (History)
2 users (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 Martin Marinschek CLA 2011-09-15 12:50:53 EDT 
Build Identifier: 2.2.1

Right now, only the SQL itself is printed. It would be very nice to have an additional info on which query resulted in this SQL. For complex queries, this is essential for fast tuning of the query.

Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:10:35 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink