-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inside [] support full SQL functions and operators [moved] #513
Comments
Hi Johann, |
Eagerly waiting for this feature. Thanks. Any plans on when 2.1-rc1 will be available? |
2.1-rc1 was supposed to be released today, but we had a small regression with Lucene, so it will be released in the next 24h. This feature has been moved to 2.1-rc2. @luigidellaquila can you confirm it? |
OK, thanks. Waiting for 2.1-rc2 will not be so bad since we know that it is close enough. |
I'm afraid it's not trivial with current query executor, but I'll see what I can do |
Thanks for the update. I know your hands are full with a lot of stuff. So this is just nice to have to write shorter and easier to grasp queries but as long as there other ways to achieve the same, I don't think it is a priority. |
@lvca @luigidellaquila any news on this issue? |
Fixed in 2.1.x and develop branches. The fix will be released with 2.1.12 Closing, please reopen if you see any unexpected behaviors Thanks Luigi |
Documentation should be updated I guess: |
Hi @karolmie1 Updated, thanks! The docs will be re-generated in short. Luigi |
This is Issue 513 moved from a Google Code project.
Added by 2011-08-19T11:45:28.000Z by l.garu...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Enhancement, Priority-Low, v2.1
Original description
The text was updated successfully, but these errors were encountered: