Through the Java client, querying data results in retrieving data that no longer exists, while querying on the web page is correct. The SQL for page data querying and web querying is consistent

[a-drop-of-tears]

Through the Java client, querying data results in retrieving data that no longer exists, while querying on the web page is correct. The SQL for page data querying and web querying is consistent

java-client
orientdb 3.2.29
jdk 1.8

The total number of query results is incorrect, and test6 is deleted data. The results refreshed by the client each time are different, but they are consistent on the web end

[tglman]

Hi,

This is strange, are there running transactions when you execute that query ?

Regards

[a-drop-of-tears]

No transaction

[a-drop-of-tears]

Issues that appear in other environments are not reproducible in the local environment. The difference is that there are other vertex classes with spaces, and an error occurs (the error screenshot is not provided) when deleting the vertex record without spaces. However, the database shows that the record has been deleted, and it will appear after refreshing repeatedly. Renaming the class with spaces and restarting the Java program resolves the issue

[a-drop-of-tears]

Through begin; insert into vertex table xxxx; insert into edge table xxx
commit; If the edge table does not exist, the database will not create records, but the Java client can query them out
@tglman