igfraud.org>
Sent: 25 June 2017 20:14
To: SQLite mailing list<mailto:sqlite-users@mailinglists.sqlite.org>
Subject: Re: [sqlite] operator precedence
On 25 Jun 2017, at 7:59pm, J Decker <d3c...@gmail.com> wrote:
> SQL Standard
> http://web.cecs.pdx.edu/~len/sql1999.pdf
>
On 25 Jun 2017, at 7:59pm, J Decker wrote:
> SQL Standard
> http://web.cecs.pdx.edu/~len/sql1999.pdf
> doesn't seem to have math operators... and the precedence tables are
> described in longhand without a simple table
> DateTimes have math operators
>
> "Operations on
Mysql has bitwise & before |
https://dev.mysql.com/doc/refman/5.7/en/operator-precedence.html
TSQL (MSSQL) has them equal.
https://docs.microsoft.com/en-us/sql/t-sql/language-elements/operator-precedence-transact-sql
Oracle doesn't have bitwise & and |
On Sun, Jun 25, 2017 at 11:11 AM, x wrote:
>
> Is there a reason why sqlite doesn’t follow the c convention?
>
> e.g. & and | have equal precedence in sqlite.
>
I'd blame it on Postgresql operator precedence; but then it also doesn't
seem to have bitwise & and | just
x wrote:
> Is there a reason why sqlite doesn’t follow the c convention?
Yes. That reason is named "ISO/IEC 9075", but commonly called
"the SQL standard".
Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
Is there a reason why sqlite doesn’t follow the c convention?
e.g. & and | have equal precedence in sqlite.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
6 matches
Mail list logo