It won't do any good to break the table into smaller tables in the same database. SQLite throws all the tables into one large pool that it manages as a single "heap", so you still get offsets as large as the overall database size.
You'd have to put the different tables into different database files. On Jan 14, 7:37 pm, asierra01 <[email protected]> wrote: > What you have is a database/dba issue not an android issue > > Lets say you have 1 database ( may be with 1 table 8G in size) > BRAKE the database in > 1 Table that will hold some kind description (metadata) of what the > BIG01, BIG02, BIG03, BIG04 tables have > BIG1, BIG2, BIG3...,BIG99 will have at most 100K records , lets > say and will potentially be as big as 100MB? 300M ? in size or less > This table will have three fields (first_rec_key, last_rec_key, > table name) > Table1-> > (0, 50000,'BIG1') > (500001, 1000000, 'BIG2') > (1000001, 400000, 'BIG3') > .... > (800000, 9000000, 'BIG78') > you start by looking in this table that only has 100 records > it will tell you the key you need is in BIG56, which is 100M, > now you use your current method of finding your record, just > instead of looking on 2GB table > you look into 100M or 300M BIG56 table. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
