[Hibernate-JIRA] Created: (HBX-906) Support better readable results when toString isn't implemented for "select new SomeObject(p1, p2, p3)" statements
12:48 p.m.
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
12:50 p.m.
New subject: [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
12:54 p.m.
New subject: [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:
------------------------------------
By the way, when the toString() method isn't implemented, you still see the same
object reference results duplicated (see HBX-905)
0 1 2
SomeObject@19cd8ea SomeObject@19cd8ea SomeObject@19cd8ea
SomeObject@65168f SomeObject@65168f SomeObject@65168f
SomeObject@ac1d0e SomeObject@ac1d0e SomeObject@ac1d0e
SomeObject@1a79e4 SomeObject@1a79e4 SomeObject@1a79e4
SomeObject@9cd89b SomeObject@9cd89b SomeObject@9cd89b
SomeObject@11c00d8 SomeObject@11c00d8 SomeObject@11c00d8
...
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
6:37 p.m.
New subject: [Hibernate-JIRA] Closed: (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=all ]
Max Rydahl Andersen closed HBX-906:
-----------------------------------
Resolution: Rejected
if you do select new we can't know how to get p1, p2 and p3 from that select new
object.
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
7 p.m.
New subject: [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:
------------------------------------
You *can't know* or you currently don't have the information at your fingertips?
One way of doing might be to transform "select new Obj(p1, p2, p3) from..."
under the covers into "select p1, p2, p3 from..." This way, the results come
back in a nice, orderly, decomposed fashion every time - and you still have the semantic
equivalent to what the user actually typed.
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
2:04 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on HBX-906:
-----------------------------------------
You *can't know* or you currently don't have >the
information at your fingertips?
the hql parser does this transformation internally and I don't have access to the
resulting resulttransformer - and even if I had it can't tell me what the return type
is.
One thing I could probably do/detect is that there is only one object available in the
actual row and just not put values into those remaing rows.
One way of doing might be to transform >"select new Obj(p1,
p2, p3) from..." under the >covers into "select p1, p2, p3 from..." This
>way, the results come back in a nice, orderly, >decomposed fashion every time - and
you still >have the semantic equivalent to what the user >actually typed.
But then you can't test if the query you want to execute actually can be
executed...;)
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
2:04 a.m.
New subject: [Hibernate-JIRA] Reopened: (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=all ]
Max Rydahl Andersen reopened HBX-906:
-------------------------------------
reopen since just not showing anything (or a ?) in the "superflous" columns.
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
4:46 a.m.
New subject: [Hibernate-JIRA] Closed: (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=all ]
Max Rydahl Andersen closed HBX-906:
-----------------------------------
Resolution: Fixed
Fix Version: 3.2beta10
ok - i've changed the rendering of the result to put ? in this specific case.
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
Fix For: 3.2beta10
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
10:01 a.m.
New subject: [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:
------------------------------------
reopen since just not showing anything (or a ?) in the
"superflous" columns.
There was a separate case for the suplerfluous columns - HBX-905.
But then you can't test if the query you want to execute actually
can be executed...;)
I agree.
My first comment on this issue suggested that we give the user a WARNING in the Problems
view (or the error log), because there's no way you can verify if
"SomeObject@19cd8ea" is right. Do you think that's a good idea? If so, can
we just tweak the title of the issue accordingly and re-open?
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
Fix For: 3.2beta10
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
6528
days inactive
6532
days old
hibernate-issues@lists.jboss.org
8 comments
2 participants
participants (2)
-
Joseph Marques (JIRA) -
Max Rydahl Andersen (JIRA)