So maybe this is done to relieve the parser for doing the semantic check,
and so improve query speed..
Well, if that's the reason, maybe is better that way.
Thanks. And sorry about the repost, it won't happen again.
Regards
On Sat, Oct 16, 2010 at 9:16 AM, Drake Wilson wrote:
> Quoth Germán H
Quoth Germán Herrera , on 2010-10-16 00:10:23 -0300:
> As you may know, both MySQL and SQL Server engines would refuse to run
> the last query, indicating an error because not all columns come from
> aggregate functions and there is no "group by" clause..
>
> Is this left on purpose?, can this beh
Anyone?
On 10/16/2010 12:10 AM, Germán Herrera wrote:
> Hi all
>
> I found the following strange behavior. It's rather easy to stumble upon
> with:
>
> sqlite> create table a(id,name);
> sqlite> insert into a values (1,'name1');
> sqlite> insert into a values (2,'name2');
> sqlite> select * from
Hi all
I found the following strange behavior. It's rather easy to stumble upon
with:
sqlite> create table a(id,name);
sqlite> insert into a values (1,'name1');
sqlite> insert into a values (2,'name2');
sqlite> select * from a;
1|name1
2|name2
sqlite> select count(*), name from a;
2|name2
sqlite>
4 matches
Mail list logo