Michael MacFadden

Another option is to update the schema to allow for null values in this condition. Right now we have the combination of not being able to compute the old value,...

Thanks for reporting. This does seem like a bug. I do believe we are using the built in OrientDB connection pooling capability. In general, we would expect that the connection...

Finally getting to look at this error. I did confirm that the error is inside OrientDB client code. Here specifically: https://github.com/orientechnologies/orientdb/blob/3c1a6e6a9a18ecc0312058ac9f2ba86cd2365594/client/src/main/java/com/orientechnologies/orient/client/remote/OStorageRemote.java#L348 We are using the OrientDB connection pooling, so this...

You are correct, this feature does not exist. I think this would be pretty easy to add. We will add this shortly.

The client side is not too complicated. We would love to collaborate with you.

We are working on this now. This will likely involve a small breaking API change. RIght now we have the following method: ``` public connectWithPassword(credentials: IUsernameAndPassword | (() => Promise)):...

One thing I did find, looking at the domain schema it appears that email is not a unique constraint for domain users. I would think we would need to make...

Greetings. Can you provide a simple set of steps to reproduce this? We'd be happy to take a look. In generally we make heavy use of ephemeral models and in...

Greetings. Can you give an example of the kind of business logic you would like to validate?

At this time, this is not supported but it is on the road map.