|
|
Posted by Tony Rogerson on 08/22/06 07:20
> This is just how God punishes people for using proprietary code :)
> Since this is MS-only
> syntax, they can do anything they wish from release to release. Ergo,
> you are screwed and live at their whim without recourse to a
> higherauthority.
>
As ever you are talking utter rubbish.
It takes 2 or 3 or sometimes more releases to deprecate and then discontinue
a feature, actually - thats better than the standard SQL cycle where you
only get 4 year was it celko? And you don't get any warning there either
unless you subscribe and pay the fees.....
> Drop an email to the publisher, so they can fix it in the book and use
> the Standard. MAX() syntax you provided. Since it is Standard SQL, MS
> has to keep it the same from release to release.
>
So, just how would you using standard SQL do the equivelant of this without
using a 'scratch tape' or relying on the application to dig you out of the
featureless ansi sql standard?
-- Get last 3 most recent sales...
select ...
from sales
where orderid in (
select top 3 orderid
from sales
order by orderdate desc
)
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"--CELKO--" <jcelko212@earthlink.net> wrote in message
news:1156180035.849964.264800@b28g2000cwb.googlegroups.com...
>>> My code can continue on, but I want to understand why the statement I
>>> constructed by following the example in my book was rejected. Did I
>>> miss something? Or is there an error in the book? Or is there a bug in
>>> SQL Server 2005? <<
>
> This is just how God punishes people for using proprietary code :)
> Since this is MS-only
> syntax, they can do anything they wish from release to release. Ergo,
> you are screwed and live at their whim without recourse to a
> higherauthority.
>
> Drop an email to the publisher, so they can fix it in the book and use
> the Standard. MAX() syntax you provided. Since it is Standard SQL, MS
> has to keep it the same from release to release.
>
Navigation:
[Reply to this message]
|