Hi Jean,
try this code in the class ObjectStorer
OObjectIteratorClass<Order> i = tx.browseClass(Order.class) ;
for (Order or : i){
or.getName();
List<OrderItem> listOrderItem=or.getItems();
for(OrderItem it:listOrderItem){
it.getName();
it.getId();
it.getValue();
}
System.out.println (or);
}
Bye, Alessandro
Il giorno venerdì 29 maggio 2015 19:41:32 UTC+2, jean safar ha scritto:
>
> Hi
>
> Apologies if it is a re-post (I did try to look for a similar issue).
>
> I tried a first very simple test (orders and order items) and I am getting
> a strange following result on both 2.1-rc3 and 2.0.
>
> Again, that's my first 5 minutes test and I looked on the net and found
> similar test code , so I am not sure what's wrong with it.
>
> May 29, 2015 1:03:10 PM com.orientechnologies.common.log.OLogManager log
>
> INFO: OrientDB auto-config DISKCACHE=10,695MB (heap=3,641MB os=16,384MB
> disk=323,721MB)
>
> Order: test with :
>
> [OrderItem: item1 Id: 1 value: 1.0, OrderItem: item2 Id: 2 value: 2.0]
>
> Order: null with :
> null
>
> The lines showing null is load from the db after I have saved it. Any
> light would be appreciated.
>
> included is the code :
>
>
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
