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?
> 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.
that _is_ confusing:
* Export to Text / CSV etc. look at the table/tree etc.
* Save Value to File looks at the heap object behind the row (the one that
is detailed in the object inspector). It does not care if you actually
display one property in a column...