Re: [sqlite] sqlite3_get_table question

2008-12-29 Thread Dan
On Dec 30, 2008, at 1:29 AM, schachtobi wrote: > >> Date: Mon, 29 Dec 2008 11:20:58 +0700 >> From: Dan >> Subject: Re: [sqlite] sqlite3_get_table question >> To: General Discussion of SQLite Database >> Message-ID: <65fa0cc6-4248-4675-8100-f069423e0...@gmail.com > > >> Why (ncol+2)? > > > I mak

Re: [sqlite] SQLITE_MAX_VARIABLE_NUMBER and .import for very wide file

2008-12-29 Thread Webb Sprague
>> I am sure there is a better way to deal with 12K rows by 2500 columns, >> but I can't figure it out > > 2500 columns sounds like a nightmare to deal with > > could you perhaps explain that data layout a little? It is a download of a huge longitudinal survey (www.bls.gov/nls/nlsy79.htm) that

Re: [sqlite] confusing with how to to this in sqlite

2008-12-29 Thread Griggs, Donald
-Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Rachmat Febfauza Sent: Sunday, December 28, 2008 9:13 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] confusing with how to to this in sqlite thanks simon fo

Re: [sqlite] sqlite3_get_table question

2008-12-29 Thread schachtobi
> Date: Mon, 29 Dec 2008 11:20:58 +0700 > From: Dan > Subject: Re: [sqlite] sqlite3_get_table question > To: General Discussion of SQLite Database > Message-ID: <65fa0cc6-4248-4675-8100-f069423e0...@gmail.com > Why (ncol+2)? I make the following select statement: SELECT fname, dsize, data,

[sqlite] About clustering (GUIDs, PK offsets, etc.)

2008-12-29 Thread Alexey Pechnikov
Hello! I did find interesting article about this popular question http://blog.maxindelicato.com/2008/12/how-to-organize-a-database-tables-keys-for-scalability.html I would also like to add that  SQLite supports "attach" command due to which we are able to use a lot of database shards on a singl

Re: [sqlite] SQLITE_MAX_VARIABLE_NUMBER and .import for very wide file

2008-12-29 Thread Chris Wedgwood
On Sun, Dec 28, 2008 at 11:49:34PM -0800, Webb Sprague wrote: > I am sure there is a better way to deal with 12K rows by 2500 columns, > but I can't figure it out 2500 columns sounds like a nightmare to deal with could you perhaps explain that data layout a little? __