Hi,
That is because you do not run in tx environment, we discussed this before,
if you want to perform your operations as single atomic unit you should
make queries like:
*transactional create edge speaks from (select from User where name =
'Luca') to (select from Language where name = 'En-uk')*

in such case all changes will be atomic.

I think it is better to run graph commands in tx mode automatically to
avoid such questions.
Guys WDYT ?


On Wed, Jan 15, 2014 at 11:50 AM, Luca Garulli <[email protected]> wrote:

> Hi,
> the best way to create a bug is the issue tracker, but this is the best
> place to ask information and discuss about OrientDB. So the best is:
> 1) look at issue tracker if the error has already been fixed. Or try last
> snapshot ("develop" branch of github)
> 2) if the problem persists even in latest version, open a new issue to be
> tracked
>
> Lvc@
>
>
>
> On 15 January 2014 10:07, SHak <[email protected]> wrote:
>
>> Is this the appropriate place to create bugs?  This is obviously a
>> serious one as we cannot trust a database once it allows duplicate edges on
>> unique index.  I don't want it lost among group discussions or are the
>> developers keeping an eye on bugs reported here.  please advice to better
>> do my part properly.
>>
>>
>> On Tuesday, January 14, 2014 4:33:05 PM UTC+2, SHak wrote:
>>>
>>> Using version 1.6.3.  I am able to create duplicate edge on every second
>>> attempt to create edge.  I have Vertex for User and for Language and an
>>> Edge speaks between the User and Language.
>>>
>>> On first attempt to create an edge, it succeeds. *create edge speaks
>>> from (select from User where name = 'Luca') to (select from Language where
>>> name = 'En-uk');*
>>> 2nd attempt to create the same edge, it gives me a warning that unique
>>> index exists and refuses to create the edge.
>>> 3rd attempt works.
>>> 4th attempt fails and so on.
>>>
>>> It seems that once an exception is thrown the next request will create a
>>> duplicate.  is the way I'm creating my index is wrong?
>>>
>>> *Data Setup:*
>>> ==========================================================
>>> #create classes/vectors
>>> create class User extends V;
>>> create class Language extends V;
>>>
>>> #create edges
>>> create class speaks extends E;
>>>
>>> #create User Data
>>> create vertex User set name = 'Luca';
>>> create vertex User set name = 'Joe';
>>>
>>> #create Language Data
>>> create vertex Language set name = 'En-uk';
>>> create vertex Language set name = 'En-us';
>>> create vertex Language set name = 'Fr-fr';
>>> create vertex Language set name = 'Ru-ru';
>>> create vertex Language set name = 'Ar-sy';
>>>
>>> #index
>>> create property speaks.out LINK;
>>> create property speaks.in LINK;
>>> CREATE INDEX unique_speaks ON speaks (in, out) UNIQUE;
>>>
>>> ===============================================
>>>
>>>
>>>   --
>>
>> ---
>> 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/groups/opt_out.
>>
>
>  --
>
> ---
> 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/groups/opt_out.
>



-- 
Best regards,
Andrey Lomakin.

Orient Technologies
the Company behind OrientDB

-- 

--- 
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/groups/opt_out.

Reply via email to