Christian Himpe

Using a subquery as a workaround, like: ``` SELECT FROM (SELECT name, publicationYear FROM metadata) ORDER BY publicationYear ``` returns the correct number of results and still uses the index...

Here is a simple case reproducing the duplication in the index: ``` CREATE DOCUMENT TYPE doc; CREATE PROPERTY doc.num LONG; CREATE INDEX ON doc (num) NOTUNIQUE; ``` then: ``` INSERT...

Wrapping the inserts in a transaction: ``` BEGIN; INSERT INTO doc SET num = 1; INSERT INTO doc SET num = 2; INSERT INTO doc SET num = 2; INSERT...

Works! Very Cool. Thank you very much @lvca

Here is a minimal example: ```sql CREATE DOCUMENT TYPE doc; CREATE PROPERTY doc.num LONG; CREATE INDEX ON doc (num) UNIQUE; ``` ```sql INSERT INTO doc SET num = 0; INSERT...

Works for me. Awesome! Thank you very much.

Unfortunately, a `REBUILD INDEX *` in an async HTTP command can still can cause an error: ```log Error on rebuilding index 'metadata_2_4579875538774': Asynchronous queue 0 is stalled. This could happen...

@lvca Could the solution to this issue be adding a procedure call to `setDefaultValues(record)` to this line: https://github.com/ArcadeData/arcadedb/blob/main/engine/src/main/java/com/arcadedb/database/LocalDatabase.java#L880 (compare https://github.com/ArcadeData/arcadedb/blob/main/engine/src/main/java/com/arcadedb/database/LocalDatabase.java#L820 )?

I have records where a timestamp is set via `default sysdate('YYYY-MM-DD HH:MM:SS')`. Now when the record gets updated meaning overwritten the timestamp needs to be renewed. I was expecting that...

If setting a default value on every update is a problem, then I guess it should at least happen for `mandatory` properties otherwise the error described above can still happen....