Re: [orientdb] Re: New attachment/detachment model for graph elements.

2015-01-06 Thread Luca Garulli
Exactly, it's automatic. Lvc@ On 6 January 2015 at 16:51, Keith Freeman <8fo...@gmail.com> wrote: > Andrey- Does this mean that in the new automatic mode it is never > necessary to call detach() or attach()? > > On Thursday, November 20, 2014 6:13:22 AM UTC-7, Andrey Lomakin wrote: > >> Hi all

[orientdb] Re: New attachment/detachment model for graph elements.

2015-01-06 Thread Keith Freeman
Andrey- Does this mean that in the new automatic mode it is never necessary to call detach() or attach()? On Thursday, November 20, 2014 6:13:22 AM UTC-7, Andrey Lomakin wrote: > > Hi all. > > Small announcement of changes in attachment/detachment policy. > Now we support 2 modes manual and auto

Re: [orientdb] Re: New attachment/detachment model for graph elements.

2015-01-05 Thread Keith Freeman
Good question, this is really the first detach() call on the vertex, immediately after loading it from a query. This code worked fine with 2.0-M3, but now throws NPEs with 2.0-rc1, so I guessed it must be due to the changes described by Andrey in this thread. Again I'm not sure from Andrey's

Re: [orientdb] Re: New attachment/detachment model for graph elements.

2015-01-04 Thread Luca Garulli
Hi, How is possible the "graph" property is null? Did you already detach it? However I've just added an additional check on that part of code. Lvc@ On 4 January 2015 at 21:30, Keith Freeman <8fo...@gmail.com> wrote: > Yes, it still throws an NPE in the latest code from your "develop" branch > a

Re: [orientdb] Re: New attachment/detachment model for graph elements.

2015-01-04 Thread Keith Freeman
Yes, it still throws an NPE in the latest code from your "develop" branch as of 5 minutes ago: public OrientElement detach() { // EARLY UNMARSHALL FIELDS getRecord().setLazyLoad(false); getRecord().fieldNames(); // COPY GRAPH SETTINGS TO WORK OFFLINE settings = graph.settings.c

Re: [orientdb] Re: New attachment/detachment model for graph elements.

2015-01-04 Thread Keith Freeman
Sure, but what is the recommended way to use the new automatic mode? Should I just avoid detach/attach completely? Or was the NPE just a bug and I should keep using detach/attach as I have in the past? On Sunday, January 4, 2015 8:52:42 AM UTC-7, Lvc@ wrote: > > Hi Keith, > Could you try with

Re: [orientdb] Re: New attachment/detachment model for graph elements.

2015-01-04 Thread Luca Garulli
Hi Keith, Could you try with 2.0-SNAPSHOT to see if the error if still present? Lvc@ On 3 January 2015 at 02:57, Keith Freeman <8fo...@gmail.com> wrote: > So I just ran into this switching from 2.0-M3 to 2.0-rc1. Suddenly all my > calls to detach() are throwing NPE exceptions, is that what's s

[orientdb] Re: New attachment/detachment model for graph elements.

2015-01-02 Thread Keith Freeman
So I just ran into this switching from 2.0-M3 to 2.0-rc1. Suddenly all my calls to detach() are throwing NPE exceptions, is that what's supposed to happen? Should I just remove all my detach() calls and let the "automatic" mode handle it for me? On Thursday, November 20, 2014 6:13:22 AM UTC-7