Thanks Richard - the View approach is fine for my needs - just wanted to know what the rationale was for the imposter tables given the ability to simulate the imposter table with a view.
Paul Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 15 June 2017 at 00:09, Richard Hipp <d...@sqlite.org> wrote: > On 6/14/17, Paul Sanderson <sandersonforens...@gmail.com> wrote: > > I am just taking a look at imposter tables and while the implementation > is > > neat I am just wondering what their use is, or rather what they can > achieve > > that a view can't achieve (and without the risk of DB corruption). > > Imposter tables are used by the RBU extension > (https://www.sqlite.org/rbu.html) to allow indexes to be updated > independently from tables, and in key order, for reduced write > amplification and improved efficiency during bulk updates. > > Minor coding errors in the use of imposter tables can corrupt the > database. If you feel you ust use them, do so with with great care. > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
