Thanks Richard
I understand how it works, quite simple really, and knowing they are used
by the RBU extension explains why.
I am working on a book and I just wanted to understand how/where it could
be used where a view, created on the same columns in an index, couldn't be.
Paul
On 2017/06/15 10:15 AM, Paul Sanderson wrote:
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.
I'm thinking the easiest way to describe it is perhaps in
On 6/14/17, Paul Sanderson 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
> On Jun 14, 2017, at 4:52 AM, Paul Sanderson
> wrote:
>
> I am just taking a look at imposter tables and while the implementation is
> neat I am just wondering what their use is
Well, right near the top of the page it says "Imposter tables are intended for
I didn't know about this functionality. I know it is a 'sharp tool', but
what I've gathered out by reading the document is that this only affects
indexes, and if I understand the doc, only when the imposter table is
created or is used to modify the indexes. What if an imposter table is
created
Can you create an imposter table on a view. A view has no associated b-tree
so I would think not!
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
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).
For instance an imposter table created on an index such as the following
from
7 matches
Mail list logo