[orientdb] Added remote connection capabilties

[kruthar]

Had to implement a separate init path for remote connections using OServerAdmin. The old, local init path is essentially the same as before.

OrientDB does not support the iterator methods that scan is built off of for remote connections, so had to check for that and record NOT_IMPLEMENTED. Made a note of that in the README as well.

[busbey]

This is surprising.

[kruthar]

Yes, a remote connection can be used to connect to a long living plocal or memory database on the server. Memory databases stored on the server don't die like local memory databases do. This being the case you could have two databases with the same name but different types, and so when doing any administration of remote databases you have to know the storage type.

[risdenk]

Should this default to true since other bindings default to remote?

[kruthar]

Whether or not the connection is a remote connection is purely dependent on the url provided by the user, so really there is not default. isRemote is defaulted to false because it is only set to true if the user provides a remote connection url, in any other case (user provides a local url) it should be false.

[kruthar]

Made a few edits:

• Added a note in README about newdb
• No longer honoring newdb if in the transaction phase. Had to modify core to push the dotransactions property to the workload as that information wasn't currently available downstream.
• Propagating DBExceptions in init()
• Found it unnecessary to split the url, no just passing the server url which is safer.

[risdenk]

Looks good to me.

[busbey]

+1