select with explicit fields will pack by fake record ?

[paynechu]

fake record packed again ?
so we need always duel with them ?
I suppose just return @Rid, @Version and roles.
tested version: 1.7-SNAPSHOT (develop) and 1.6.6

[lvca]

This seems a bug of Studio, may you open the very same issue in: https://github.com/orientechnologies/orientdb-studio/issues?state=open

[paynechu]

I don't think this only Studio bug.
Because I also got same return from Binary Protocol.

[lvca]

With the console or API? If the console, after the result, can you execute:

display record 0

[paynechu]

I think this issue is everywhere not only Studio.
console and binary protocol (self implemented driver) all return same result

[lvca]

So the items are present, and by default the collections show only the size. The problem is not in OrientDB but in Studio.

[paynechu]

why Studio ?
you can see the console's resultset also packed by fake record
id suppose is #5:0 but now is #-2:1 same as Studio

what I expect the result should like

----------------------------------------------------------------------------
ODocument - Class: OUser     id: #5:0        v.1
----------------------------------------------------------------------------
          roles : [#4:0-#4:0]

But now like

----------------------------------------------------------------------------
ODocument - Class: null     id: #-2:1        v.0
----------------------------------------------------------------------------
              rid : #5:0
       version : 1
          roles : [#4:0-#4:0]

That mean a fake record packed it

[lvca]

I thought you was referring to the collection, sorry. However it's normal. Every time you do a projection in select OrientDB creates a temporary record to host the result. If you do:

select from ouser

You'd have what you expecting. This is to avoid you save back the documents: all the missing fields would be removed.

[paynechu]

sure if I always get all fields~
But I think avoid to save partial data back to database should user(app developer) job right ?
seems should not the database's job.
and the class name also missed ~ so make the partial query less useful

[lvca]

You could also use include() or exclude() functions to remove things from the result set.

[paynechu]

include and exclude seems for embedded fields.
no help on this issue

[paynechu]

I suggest should mark this issue to improvement not invalid
I don't see other database will treat the partial query is another record
Just helping to improve OrientDB.

[lvca]

Why do you need partial results?

[paynechu]

Why not ?
not everyone always just use ORM right ?

[lvca]

We can't support this because as I said, once back the record could be updated with its rid. This will generate many common pitfalls for users.