[GitHub] [incubator-age] bravius commented on issue #161: Index is lost after using SET clause

bravius commented on issue #161: URL: https://github.com/apache/incubator-age/issues/161#issuecomment-1038600992 @JoshInnis - It's still an issue. CREATE throws errors on index duplicates, but SET does not. -- This is an automated message from the Apache Git Service. To respond to the

[GitHub] [incubator-age] bravius commented on issue #161: Index is lost after using SET clause

bravius commented on issue #161: URL: https://github.com/apache/incubator-age/issues/161#issuecomment-1035612877 @pdpotter Okay I just checked that. When CREATE-ing a vertex with a duplicate key, I get "duplicate key value violates unique constraint", as expected.

[GitHub] [incubator-age] bravius commented on issue #161: Index is lost after using SET clause

bravius commented on issue #161: URL: https://github.com/apache/incubator-age/issues/161#issuecomment-1014861860 Hey bud, I was also looking for an indexing solution, so I just re-worked your function as a plpgsql function. It seems to work as expected now, throws error on duplicates.