[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-906) Support better readable results when toString isn't implemented for "select new SomeObject(p1, p2, p3)" statements
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-906?page=co...
]
Joseph Marques commented on HBX-906:
------------------------------------
I'm just trying to make the tools better usable out of the box. I think it's
important to implement the toString method, so perhaps you could also drop a WARNING into
the Problems view (or the error log) saying that it's a good idea to implement it.
Support better readable results when toString isn't implemented
for "select new SomeObject(p1, p2, p3)" statements
------------------------------------------------------------------------------------------------------------------
Key: HBX-906
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-906
Project: Hibernate Tools
Type: New Feature
Versions: 3.2beta8
Reporter: Joseph Marques
If I have some class called SomeObject WITHOUT a toString method, and I have some
statement like "select new SomeObject(p1, p2, p3)", the results look like
0
SomeObject@19cd8ea
SomeObject@65168f
SomeObject@ac1d0e
SomeObject@1a79e4
SomeObject@9cd89b
SomeObject@11c00d8
...
Instead, why not attempt to show the results as:
0 1 2
<p1.toString()> <p2.toString()> <p3.toString()>
<p1.toString()> <p2.toString()> <p3.toString()>
<p1.toString()> <p2.toString()> <p3.toString()>
In other words, statements like "select new SomeObject(p1, p2, p3) ..." should
default to the same results that "select p1, p2, p3 ..." would.
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira