On 5/3/06, E Tse <[EMAIL PROTECTED]> wrote:
Hi Jay, Thanks for your reply. I don't think I can use the attach statement. I thot attach statement can combine different databases, but not on a database with a single table. I think at best it could split a large db file by splitting the tables within the database (if there are multiple tables).
No, that won't work for a single table.
I would be nice if sqlite implement the underlying file engine not with a single file, but optionally with a different engine which is implemented by multiple smaller files (by filesize). This might help the underlying OS to manage file caches better, IMO.
I believed some databases were putting data in separate partitiions etc. so the database engine could manage the cache not the operating system. "Gaming the cache" by changing the design of the database seems like a pretty version specific idea. Worse yet, the behaviour of the cache isn't a guaranteed part of the operating system specs. It might not always work even on the same operating system.. The cache sizes of disk drives are changing. Cache designs can be changed at any time without any visibility to the code, and new file systems are introduced regularly. What will reiser4 do to performance etc? This seems like a tricky change with a good chance of being problematic.
