Re: Future suggestion

2001-02-22 Thread Jason Landry
> Also, specifying fields won't break things when people add fields to a > table. Yeah, but you already have the same problem with SELECT *. Let me give another example. You have a table with 15 rows. One of those rows is TEXT. You really do want everything except the text. Doesn't anyone e

RE: Future suggestion

2001-02-21 Thread Cal Evans
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 wan

RE: Future suggestion

2001-02-21 Thread William R. Mussatto
Also, specifying fields won't break things when people add fields to a table. On Wed, 21 Feb 2001, Cal Evans wrote: > Date: Wed, 21 Feb 2001 11:07:36 -0600 > From: Cal Evans <[EMAIL PROTECTED]> > To: Jason Landry <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Subject: R

Re: Future suggestion

2001-02-21 Thread Jason Landry
an 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 sugges