Notice two issues while playing around with the database. Using the latest from Git. Downloaded this afternoon from the "develop" branch. Version 1.6.4.
1. Create two Vertices (A and B) and connect with an Edge. Call the binary method, REQUEST_RECORD_UPDATE to update Vertex A. This clears all existing data (Not sure when this clears, I would have thought REQUEST_CLEAN_OUT would clear) including the "in" and "out" created by the edge. Vertex A now has everything cleared except the new properties. Here is where it gets a little funky... The edge still exists (should be deleted) and says it is still connected to A and B. When going into B (via OrientDB studio) it says it is still connected to the edge. But when going into A, there are no incoming or outgoing. Two solutions: Either the edge should be deleted on an UPDATE if everything is cleared. Or on an UPDATE, new properties are added and existing are replaced. 2. Creating a new class with an invalid cluster id will corrupt the whole database. When trying to open the database that has a class with an invalid or nonexistent cluster id will throw an error and refuse to open: 2014-01-22 16:06:09:663 SEVE Internal server error: java.lang.IllegalArgumentException: Cluster name is empty [ONetworkProtocolHttpDb] Is there a way to prevent the database from saving a class with an empty cluster name? Or if an empty cluster name is found, automatically remove it so it will not kill the whole database? Thanks! -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
