Conversation
9688f49 to
80e82d4
Compare
|
@billy1624 @tyt2y3 can you review?) I have done. |
billy1624
left a comment
There was a problem hiding this comment.
Hey @ikrivosheev, thanks!!
Based on the docs and experiment result. Seems that SQLite only support EXISTS. The other three ANY, SOME and ALL are not supported.
- https://sqlite.org/lang_expr.html#the_exists_operator
- https://dbfiddle.uk/?rdbms=sqlite_3.39&fiddle=201457e4ee750fb8972847041a736e19
Also, it'd be best if we have doc test for subquery operators to be used in condition. Such as...
SELECT s1 FROM t1 WHERE s1 > ANY (SELECT s1 FROM t2);
SELECT s1 FROM t1 WHERE s1 <> ANY (SELECT s1 FROM t2);
SELECT s1 FROM t1 WHERE s1 <> SOME (SELECT s1 FROM t2);|
@billy1624 @tyt2y3 hello! I have small question. Expr::ne have signature: What is the best way to name new methods? For example:
|
|
Hey @ikrivosheev, good suggestions!! I do think we need |
@billy1624 hello! Done |
|
Hmm, @billy1624, I think about new method... Maybe is better |
@tyt2y3 what do you think about it? |
c9da3a1 to
fb8bb71
Compare
|
@billy1624 @tyt2y3 done! I add |
|
@billy1624 @tyt2y3 can you review this PR? |
| impl<T> From<T> for SimpleExpr | ||
| where | ||
| T: Into<Value>, |
There was a problem hiding this comment.
Interesting... I was thinking of the potential drawbacks of this blanket impl but could not think of one.
This should improve ergonomics a lot in the end.
PR Info
EXISTS (subquery)operator #118Adds
EXISTS,ALL,ANY,SOME