Re: [sqlite] SELECT * vs SELECT columns ?

On Thu, Oct 29, 2009 at 3:19 PM, Gerry Snyder wrote: > Beau Wilkinson wrote: >> >>  If the schema changes, a listing of every column can be invalidated, but >> the asterisk cannot > > OTOH, a listing of every column may catch a query which is no longer > valid,

Re: [sqlite] SELECT * vs SELECT columns ?

On Thu, Oct 29, 2009 at 2:59 PM, John Crenshaw wrote: >> If the schema changes, a listing of every column can be >> invalidated, but the asterisk cannot. > > This is only partly true. At some point, the code is going to need to > grab the individual fields, and that is

Re: [sqlite] SELECT * vs SELECT columns ?

> If the schema changes, a listing of every column can be > invalidated, but the asterisk cannot. This is only partly true. At some point, the code is going to need to grab the individual fields, and that is the point where the asterisk fails to serve you well. If new fields are added to the

Re: [sqlite] SELECT * vs SELECT columns ?

On Behalf Of Kristoffer Danielsson Sent: Wednesday, October 28, 2009 12:51 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] SELECT * vs SELECT columns ? I don't know about SQLite, but in all SQL courses you learn that you should NEVER use the asterisk. The asterisk is merely there to le

Re: [sqlite] SELECT * vs SELECT columns ?

...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Kristoffer Danielsson Sent: Wednesday, October 28, 2009 12:51 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] SELECT * vs SELECT columns ? I don't know about SQLite, but in all SQL courses you learn that you should NEVER use

Re: [sqlite] SELECT * vs SELECT columns ?

Re: [sqlite] SELECT * vs SELECT columns ? > > I would expect there to be a speed and memory performance *impact* if > the result set contains columns other than the three specified ones, > since obviously the library will need to allocate more memory to hold > the extra data.

Re: [sqlite] SELECT * vs SELECT columns ?

I would expect there to be a speed and memory performance *impact* if the result set contains columns other than the three specified ones, since obviously the library will need to allocate more memory to hold the extra data. On 10/28/2009 03:52 PM, Pete56 wrote: > I am searching across two

[sqlite] SELECT * vs SELECT columns ?

I am searching across two joined tables and am interested in a few parameters: SELECT a.first a.third b.first FROM a JOIN b ON a.RowID = b.RowID WHERE value = :value Is there any speed or memory performance improvement by using SELECT *, rather than SELECT ? If I know there will only be one