ERROR with OrientDB 2.2

Question

ERROR with OrientDB 2.2

Closed this issue 8 years ago · 21 comments

When I started to use this driver with OrientDB 2.1.* everything is working as it should, but with 2.2 it breaks because of Protocol version 34 is not supported.

Actually the solution is really simple, you need to pass the protocol version from your constants "32" during the two connect commands(server and database) and everything works.

I just removed these lines in OrientSocket Class, and now the constant protocol version was automatically transmitted in the both connect commands.

if( $protocol > $this->protocolVersion ){
throw new PhpOrientWrongProtocolVersionException('Protocol version ' . $protocol . ' is not supported.');
}
$this->protocolVersion = $protocol;

Can you please fix this, because I really want to work with the newest version coming up.

Thank you in advance.

luclanet commented 8 years ago

+1

Ostico commented 8 years ago

Updated

🎉5

Answer 1 · 2016-05-10T15:00:32.000Z

@stefpe this might not be as easy as just switching a value to 34 or even worse - removing a line that sets the protocol version internally in the library. New protocol engine from Orient might contain improvements/changes that might lead to wrong record handling and screw you DB at some point. So be careful ))

@Ostico needs to take a more thorough look I guess. I'm also looking forward to getting this new feat.

Answer 2 · 2016-05-10T23:05:00.000Z

Couldn't you just run the unit tests and if they pass, the protocol could be considered "functional" and more importantly, safe to use? The only possible problem after that is, the driver might not be introducing any additional/ new features added to protocol 34. But, at least you'd know the driver still works properly with 2.2. Right?

Scott

Answer 3 · 2016-05-11T03:02:40.000Z

@smolinari very true. Forgot about them tests completely ))

Answer 4 · 2016-05-11T11:47:28.000Z

I forked the project, changed the code and tried with version 2.1.* -> everything works!
Tried with version 2.2.0RC1 -> fails for tokens and some sql command tests.

Answer 5 · 2016-05-11T15:34:37.000Z

Ok. That would mean @Ostico would need to dig in and make the driver 2.2 ready. 😄

Scott

Answer 6 · 2016-05-31T18:17:47.000Z

+1 very excited to use 2.2, but the driver need to support it :(

Answer 7 · 2016-06-01T00:27:12.000Z

Upgrading. The protocol changed significantly and some issues on documentation slowed work. Will be updated as soon as possible. I apologize for the delay.

Answer 8 · 2016-06-01T02:36:04.000Z

+1 for the update! woohoo!

Answer 9 · 2016-06-05T07:36:56.000Z

+1 for the update

Answer 10 · 2016-06-06T13:13:57.000Z

+1 for the update

Answer 11 · 2016-06-16T09:46:14.000Z

@Ostico Any news on the 2.2 compatibility?

Answer 12 · 2016-06-16T10:29:56.000Z

Hi all.
I started to work on that, but this month i'm really busy. I only upgraded the python driver at moment. I can continue starting from Wednesday.

Answer 13 · 2016-06-16T10:40:01.000Z

@Ostico thanks for the reply. Eagerly waiting on the update. Good luck!

Answer 14 · 2016-06-16T10:53:30.000Z

@Ostico - If you need any support with documentation, doc proof reading, simple PHP programming tasks, please let me know.

Scott

Answer 15 · 2016-06-16T16:16:46.000Z

@Ostico similar, willing to offer help with the php driver, just let me know of a task or two that could help ease your load

Answer 16 · 2016-06-16T16:27:05.000Z

@Ostico same here!

Answer 17 · 2016-06-16T17:34:13.000Z

@Ostico me too!

Answer 18 · 2016-06-23T23:36:59.000Z

a week later, any further update? Thank you

cheers

Answer 19 · 2016-06-27T05:08:21.000Z

Today i tried to upgrade to 2.2 i also faced with this issue.

Waiting is not best thing but it's nice to see we have some community here, and i am not alone :)