[
https://issues.apache.org/jira/browse/DERBY-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661086#action_12661086
]
Knut Anders Hatlen commented on DERBY-4000:
-------------------------------------------
Thanks for checking the standard, Dag. If we document '!=' we should mention
that it is non-standard.
Both MySQL and PostgreSQL accept '!=' instead of '<>', according to their
documentation:
http://dev.mysql.com/doc/refman/5.1/en/comparison-operators.html#operator_not-equal
http://www.postgresql.org/docs/8.3/interactive/functions-comparison.html
> Reference manual leaves != out of list of boolean operators
> -----------------------------------------------------------
>
> Key: DERBY-4000
> URL: https://issues.apache.org/jira/browse/DERBY-4000
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.5.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
>
> Table 1, SQL Boolean Operators, at
> <URL:http://db.apache.org/derby/docs/dev/ref/rrefsqlj23075.html> lists the
> comparison operators <, =, >, <=, >=, <>. Derby also accepts !=, which I
> believe has the same meaning as <>. The != operator should be documented
> along with the other operators. (I haven't checked whether != is standard
> SQL.)
> ij> select * from (values 1,2,3)v(x) where x != 2;
> X
> -----------
> 1
> 3
> 2 rows selected
> ij> select * from (values 1,2,3)v(x) where x <> 2;
> X
> -----------
> 1
> 3
> 2 rows selected
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
