Ilia Naryzhny

Support of wicket 7 implemented here: https://github.com/wicketstuff/core/tree/master/select2-parent @ivaynberg , am I right that this project was migrated to WicketStuff?

Hello, @luigidellaquila, I pass List. Here is a commit which helped to overcome this behavior of OrientDB: https://github.com/OrienteerBAP/wicket-orientdb/commit/156a173ad06776f38790a8d9ca4b60388acd0b53 It was spotted in our UI: after applying of filter to a...

@luigidellaquila , thank you! It seems that something really bad happened with IN condition (or more...). Real-life example through our REST interface: https://app.paleontology.rocks/orientdb/query/db/sql/select+from+Book+where+@rid+=+%231356:3 Please pay attention to `category` field. Now...

@luigidellaquila, checked source of `com.orientechnologies.orient.core.sql.parser.OInCondition`. Seems that there are really 2 issues: - [ ] IN treats incorrectly prepared statement on the right side - [ ] IN works literally...

Surprisingly, `CONTAINSANY` do what's we are needed. Check the example below. All documents:  Filtered:  But `CONTAINSANY` also has a defect. Check this results out: 

@luigidellaquila, please advise, was this fixed in some latest minor releases?

Why actually this bahaviour is needed? And what's actual results? Exception?

Please provide more details: screenshots, screencasts, full stacktrace and etc.

What does that mean? Can you please give example?

Am I right that expectation to have not IDs but links to documents with names?