Yeah, I totally agree with the idea of limiting the fields selected for most
operations. But it would be useful even for using something like the MySQL
client -- I want to see the majority of fields but don't care about a few
text or varchar fields. It's a pain to type in the field list every time.
I just think that an EXCEPT clause in the field list would make sense in a
lot of ways.
Too bad about Microsoft's "Not Invented Here" treatment of Visual FoxPro.
It's a much better tool than Visual Beginners All Purpose Symbolic
Instruction Code -- er, I mean Visual Basic, but that's an argument for
another list ;-).
----- Original Message -----
From: "Cal Evans" <[EMAIL PROTECTED]>
To: "Jason Landry" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, February 21, 2001 11:07 AM
Subject: RE: Future suggestion
> Hey HEY! Another old Fox-Jockey! :) (There are still a few of us left in
the
> world)
>
> While I understand your suggestion, I would suggest that you steer clear
of
> using Select * at all except when testing or when there is no other way.
You
> will get better performance by specifying the fields you want returned in
> your result set explicitly.
>
> Just my $0.02,
>
> Cal
> http://www.calevans.com
>
>
> -----Original Message-----
> From: Jason Landry [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 21, 2001 9:41 AM
> To: [EMAIL PROTECTED]
> Subject: Future suggestion
>
>
> I just started using MySQL in the past month or so, and love it so far. I
> come from a background that includes a lot of FoxPro (way back in the days
> of FoxBase for the Macintosh). I also have had a bit of MS SQL Server
> experience, but more using it as a back end for Visual Foxpro.
>
> One of the things that have always bugged me about writing a SELECT
> statement has been the inablility to exclude certain fields. When doing a
> select * from a join, it would be nice to be able to do something like
this:
>
> SELECT * EXCEPT invoice.custpo, payment.custid FROM ....remainder of
select
> statement
>
> Is there anything holding back the developers of MySQL from implementing
> such a construct in MySQL, like the goal of ANSI compatability? Am I
being
> a big dumbass for desiring such functionality?
>
> In any case, thanks to everyone who contributed to MySQL for such a cool
> product.
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
