How record_create for Edge should look like?

[rangilboa]

I tried and failed :

    class_id1 = connection.client.command( "create class my_v_class extends V" )
    class_id2 = connection.client.command( "create class my_e_class extends E" )
    rec1 = { '@my_v_class': { 'accommodation': 'house', 'work': 'office', 'holiday': 'sea' } }
    rec2 = { '@my_v_class': { 'accommodation': 'house', 'work2': 'office', 'holiday': 'sea3' } }
    rec_position1 = connection.client.record_create(class_id1, rec1)
    rec_position2 = connection.client.record_create(class_id2, rec2)

    rec3 = { '@my_e_class': {  '@to': rec_position2.rid, '@from': rec_position1.rid} }
    rec_position3 = connection.client.record_create(class_id2, rec3)

[Ostico]

Hi,
try this:

class_id1 = client.command( "create class my_v_class extends V" )[0]
class_id2 = client.command( "create class my_e_class extends E" )[0]
rec1 = { '@my_v_class': { 'accommodation': 'house', 'work': 'office', 'holiday': 'sea' } }
rec2 = { '@my_v_class': { 'accommodation': 'house', 'work2': 'office', 'holiday': 'sea3' } }
rec_position1 = client.record_create(class_id1, rec1)
rec_position2 = client.record_create(class_id2, rec2)
sql_edge = "create edge from " + rec_position1.rid + " to " + rec_position2.rid
res = client.command( sql_edge )

[rangilboa]

Is there a way to all in one transaction?

It look like only record_create is supported by tx
On Oct 4, 2014 10:32 PM, "Ostico" notifications@github.com wrote:

Hi,
try this:

class_id1 = client.command( "create class my_v_class extends V" )[0]
class_id2 = client.command( "create class my_e_class extends E" )[0]
rec1 = { '@my_v_class': { 'accommodation': 'house', 'work': 'office', 'holiday': 'sea' } }
rec2 = { '@my_v_class': { 'accommodation': 'house', 'work2': 'office', 'holiday': 'sea3' } }
rec_position1 = client.record_create(class_id1, rec1)
rec_position2 = client.record_create(class_id2, rec2)
sql_edge = "create edge from " + rec_position1.rid + " to " + rec_position2.rid
res = client.command( sql_edge )

—
Reply to this email directly or view it on GitHub
#12 (comment).

[Ostico]

Seems not to be possible, TX_COMMIT support only record update/create/delete
https://github.com/orientechnologies/orientdb/wiki/Network-Binary-Protocol#request_tx_commit
so our driver don't implement that feature.

I can ask to orientdb creators if there is a workaround or what is the right way to do that.

[rangilboa]

Thanks for the quick answer!!!

The problem I am trying to solve is

Persisting Vertices and Edges in one transaction (tx).

It looks like there is a solution for Vertices but note for Edges.

I am new to pyorientdb and maybe there is a better solution ...

ran

On Oct 5, 2014 12:13 AM, "Ostico" notifications@github.com wrote:

Seems not to be possible, TX_COMMIT support only record
update/create/delete

https://github.com/orientechnologies/orientdb/wiki/Network-Binary-Protocol#request_tx_commit
so our driver don't implement that feature.

I can ask to orientdb creators if there is a workaround or where is the
right way to do that.

—
Reply to this email directly or view it on GitHub
#12 (comment).

[Ostico]

Now you can use batch command