Re: [sqlite] Order of fields for insert

All I/O is done via page sized blocks. So the minimum amount of data to be fetched will always be a page. The bigger issue is, as you said, when you need to follow a chain of pages to get a small value at the end. -j On Thu, Oct 6, 2016 at 9:53 AM, Paul Sanderson

Re: [sqlite] Order of fields for insert

On Thu, Oct 6, 2016 at 9:25 AM, Hick Gunter wrote: > SQLite compresses rows before storing and decompresses rows before > returning fields. BLOB fields are the most time consuming to process and so > should be placed at the end of the row. Often used fields - i.e. (foreign) >

Re: [sqlite] Order of fields for insert

> Long columns, especially TEXT or BLOBs which may have lots of data in, should > go at the end. Because you don't want SQLite to have to fetch all that data > from storage just to get at the column after it. To be pedantic SQLite does not need to "fetch" all of the data from strorage before

Re: [sqlite] Order of fields for insert

ok On 6 Oct 2016 8:08 p.m., "Simon Slavin" wrote: > > On 6 Oct 2016, at 3:37pm, Krishna Shukla > wrote: > > > Help how can i import exel file in sqlite and get result in c# desktop > > application ...? > > Please start a new thread for this

Re: [sqlite] Order of fields for insert

On 6 Oct 2016, at 2:46pm, Jeff Archer wrote: > Are there any performance or other considerations of the order of the > fields for an insert? No. Order of columns in the CREATE TABLE command matters. Order they're named in operations after that doesn't. When SQLite

Re: [sqlite] Order of fields for insert

On 6 Oct 2016, at 3:37pm, Krishna Shukla wrote: > Help how can i import exel file in sqlite and get result in c# desktop > application ...? Please start a new thread for this question. Simon. ___ sqlite-users mailing

Re: [sqlite] Order of fields for insert

t; -Ursprüngliche Nachricht- > Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > Im Auftrag von Jeff Archer > Gesendet: Donnerstag, 06. Oktober 2016 15:46 > An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Betreff: [sqlite] Order

Re: [sqlite] Order of fields for insert

sers-boun...@mailinglists.sqlite.org] Im > Auftrag von Jeff Archer > Gesendet: Donnerstag, 06. Oktober 2016 15:46 > An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Betreff: [sqlite] Order of fields for insert > > Just a quick question. I am actually deciding i

Re: [sqlite] Order of fields for insert

st <sqlite-users@mailinglists.sqlite.org> Betreff: [sqlite] Order of fields for insert Just a quick question. I am actually deciding if I need to do some performance testing of this but thought I might gain some quick insight. My specific insert and table are below but really I am looking for a

Re: [sqlite] Order of fields for insert

Sorry, that was just mistake in reducing the code for the email, please ignore. What do you mean "what matters is order of columns in table"? or was that just referring to the typo? Jeff Archer jeffarch...@gmail.com On Thu, Oct 6, 2016 at 9:52 AM, Clemens Ladisch

Re: [sqlite] Order of fields for insert

Jeff Archer wrote: > Are there any performance or other considerations of the order of the > fields for an insert? No; what matters is the order of columns in the table. > INSERT INTO ​mytable(wid1,cnt,​dat,​wid3,wid2) VALUES (?,?,?,?) ​> - VS - ​ > INSERT INTO ​mytable(wid1,wid2,wid3,cnt​,dat​)

[sqlite] Order of fields for insert

Just a quick question. I am actually deciding if I need to do some performance testing of this but thought I might gain some quick insight. My specific insert and table are below but really I am looking for a general answer to the question not just this specific case. Are there any performance