| Save Value to File [message #7044] |
Fri, 14 November 2008 00:25  |
Eclipse User |
|
|
|
Originally posted by: cgrinds.us.ibm.com
I selected rows from a OQL result set and choose Copy > Save Value to File.
It didn't save what I expected, which was the string column.
This was my query:
SELECT toString(k.key) from objects (SELECT objects outbounds(x.table) FROM
OBJECTS 0x22eab878 x) k
As you can see, my sole column was a string but instead of writing the
string value to the file it wrote the object.
I realize this isn't exactly what SaveValueAsQuery was intended to do but
seems like a reasonable feature.
I looked at adding this option to SaveValueAsQuery but didn't make a lot of
progress since the actual object is an OQLQueryImpl.ResultSet.$1. Seems
like the cleanest way to solve this might be creating a different action
that has more intimate knowledge of OQL. Thoughts?
--
Chris Grindstaff
cgrinds@us.ibm.com
|
|
|
| Re: Save Value to File [message #7067 is a reply to message #7044] |
Fri, 14 November 2008 01:31  |
| Eclipse User |
|
|
|
Originally posted by: cgrinds.us.ibm.com
Chris Grindstaff <cgrinds@us.ibm.com> wrote in
news:Xns9B55C58E11987chrisibm@206.191.52.34:
> I selected rows from a OQL result set and choose Copy > Save Value to
> File. It didn't save what I expected, which was the string column.
> This was my query:
> SELECT toString(k.key) from objects (SELECT objects outbounds(x.table)
> FROM OBJECTS 0x22eab878 x) k
Ah I spoke to soon, the same functionality can be achieved using Export >
to TXT.
--
Chris Grindstaff
cgrinds@us.ibm.com
|
|
|
|
Powered by
FUDForum. Page generated in 0.02753 seconds
] 
Search
Help
Register
Login
Home
