Subject | Re: [firebird-support] what schema is better ? |
---|---|
Author | Alan J Davies |
Post date | 2010-12-09T19:25:09Z |
I'm surprised, interested and confused, although not always in that
order, by the select statement /*rant*/ from Ann. How else can you
"select" the data you want?
As for the 400th worst feature, I won't task you, because I suspect you
would know the answer!
Can't offer any more suggestions to original post.
Regards
Alan J Davies
Aldis
order, by the select statement /*rant*/ from Ann. How else can you
"select" the data you want?
As for the 400th worst feature, I won't task you, because I suspect you
would know the answer!
Can't offer any more suggestions to original post.
Regards
Alan J Davies
Aldis
On 09/12/2010 18:48, Ann W. Harrison wrote:
> On 12/9/2010 11:30 AM, Vander Clock Stephane wrote:
>
> >
> > i select the rows only like this
> >I'm surprised
> > select * from ZillionRows where OBJECTID=xxx;
> >
>
> Since you bring it up, let me rant a moment on one of
> my favorite topics.
>
> <rant>
> The *worst* feature in SQL is "select *". It's a holdover
> from an interactive pedagogical language circa 1974 that
> has no place in a programming language. It defeats the
> use of one of the major features of relational databases -
> the separation of logical and physical storage. If you
> realize after you've built your application that you really
> need a Skype handle as well as a phone number, just add it.
> As long as you've used field names in your queries, everything
> old works just the way it did and new queries and updated
> queries can use the Skype handle. But put one Select *
> into the mix and you've got chaos.
>
> The second worst is an insert without a target field list.
> I won't bore you with the third through 400th worst features
> of SQL.
> </rant>
>
> Ann
>
>
> ------------------------------------------------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 10.0.1170 / Virus Database: 426/3304 - Release Date: 12/08/10
>