Support new RethinkDB 2.1 error type hierarchy

[danielmewes]

No description provided.

[mbrevda]

It seems that errors in js is to exceptions in php. Would you call them errors or exceptions?

[danielmewes]

What I meant is just implementing an analogue of this rethinkdb/rethinkdb#4559 .
Currently we have the exception types RqlDriverError and RqlServerError. We should implement subclasses of these corresponding to the error types reported by RethinkDB 2.1.

[danielmewes]

(in all of the official RethinkDB drivers including the JS one each error type corresponds to one exception class)

[mbrevda]

I saw that. I was asking if they shouldn't be renamed in php from "Errors" to "Exceptions"?

[danielmewes]

Ah, got you.

I think it would be better to stay close to the official exception names (so people can look at http://rethinkdb.com/docs/error-types/ and immediately understand what the corresponding exception in PHP-RQL is).

I originally picked slightly different exception names from the official drivers when I first wrote PHP-RQL a few years ago, but wouldn't to the same again. It just increases the documentation work and makes the driver more confusing for users who have been reading the official documentation.

[mbrevda]

This makes sense