Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
GROUP BY 1 no longer works
Message
From
18/02/2003 18:34:20
Mike Yearwood
Toronto, Ontario, Canada
 
 
To
18/02/2003 17:18:25
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00750415
Message ID:
00754733
Views:
39
Jim

Why argue about this? Was it better to be stuck with a design that could give incorrect results since Foxpro 2.x? Just because something worked the way it worked for a really long time doesn't make it right.

They did give a way to maintain compatability with a backward design.

>Sergey,
>
>>Jim,
>>
>>You still missing the point. They fixed bugs in SQL Engine, nothing more. The ANSI compability was a result or the way of bug fixes not an addition to the bug fixes. As Gene mentioned in Re: GROUP BY 1 no longer works Message #754560, the discussion was about what make a default, VFP7 or VFP8 SQL Engine behavior.
>
>So you are saying that the removal of memo allowability in DISTINCT select queries was a requirement to FIX the known bug?
>And you are saying that the need to now include ALL SELECTed fields in GROUP BY was a requirement to FIX the known bug?
>I don't think that either is the case, personally, but it is clear to me that at least the GROUP BY **can** be attributable to ANSI SQL compatability. I believe the both could have been fixed within the existing syntax - it's a simple matter of programming.
>
>I agree that there were bugs and that they have fixed them. I don't feel that it was necessary to adopt ANSI IN ORDER TO FIX THEM.
>Now I don't object that ANSI compatibility was implemented TOO, because I think that is a good thing for the future.
>BUT it remains that I do not feel that the implementation we got was the optimal one. And it remains that we get what we get and have to live with it.
>SNIP
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform