ax
error would be returned on parsing.
is correct only up to SQL-99 standard. There was a relevant discussion in
SO: Why does MySQL add a feature that conflicts with SQL
standards?<http://stackoverflow.com/questions/7594865/why-does-mysql-add-a-feature-that-conflicts-with-sql-standards
readable and easy to edit:
https://mariadb.com/kb/en/library/with/
Best regards
Pantelis Theodosiou
On Thu, May 17, 2018 at 11:23 AM, wrote:
> You're not making a lot of sense here. Please explain the "ambiguity".
> That's a fairly complex query so you should include
etter that the
existing ones.
Pantelis Theodosiou
On Fri, May 16, 2014 at 12:11 PM, Colin Charles wrote:
> Hi!
>
> http://seonguck.blogspot.kr/2014/05/limit-rows-matched.html
>
> We have a potential contribution here for a LIMIT ROWS MATCHED feature -
> might be interesting
)
The query in question is very simple:
SELECT a AS result FROM tableXUNION DISTINCTSELECT b FROM tableX ;
I couldn't find a related bug in the MDEV.
Is this a known (or fixed) issue or should I go and add a bug report/
Pantelis Theodosiou
___
Ma
4 matches
Mail list logo
