"Miha Vrhovnik" <[EMAIL PROTECTED]> wrote: > On 3/21/2006, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > >"Miha Vrhovnik" <[EMAIL PROTECTED]> wrote: > >> Hi drh and others, > >> > >> Regarding the issues they appear on ML with very large tables and knowing > >> that sqlite now enforces constraint checks on tables, is there any > >> chances of suporting table partitoning? > >> > > > >Put each table in a separate database file then ATTACH > >the databases. > > > That's not the same. You still need to rewrite queries, where in real > table partitioning you don't need to do that.
What changes to the queries do you think are necessary? > The select's and inserts > are faster because db knows where to put/search for them. > The database already knows exactly where to look for each table when all the tables are in the same file. All it has to do is "lseek()" to the appropriate spot. How does moving tables into separate files help this or make it any faster? -- D. Richard Hipp <[EMAIL PROTECTED]>
