Re: [sqlite] equality searches and range searches with encrypted data

Thank you for your replys, but I am still not sure I understand how a Query is executed on (page) encrypted data wihout either indexing the data prior to encrption, creating a secondary hash column of the data or simply decrypting every page to get at the underlying data? Would greatly

Re: [sqlite] equality searches and range searches with encrypted data

On Sun, Aug 24, 2008 at 12:36 AM, Derek Developer <[EMAIL PROTECTED]> wrote: > Well that implies that the "parsing" decrypts each page in the database for > each query. How else would it traverse a key that is encypted? > > Isn't that going to be very slow? > Are you thinking it needs to decrypt

Re: [sqlite] equality searches and range searches with encrypted data

Well that implies that the "parsing" decrypts each page in the database for each query. How else would it traverse a key that is encypted? Isn't that going to be very slow? Cory Nelson <[EMAIL PROTECTED]> wrote: On Sun, Aug 24, 2008 at 12:07 AM, Derek Developer wrote: > I am still not clear

Re: [sqlite] equality searches and range searches with encrypted data

On Sun, Aug 24, 2008 at 12:07 AM, Derek Developer <[EMAIL PROTECTED]> wrote: > I am still not clear if page level encryption permits equality searches and > range searches? > Intuitively it would seem that these searches would require every page to be > decrypted to access the column data for

[sqlite] equality searches and range searches with encrypted data

I am still not clear if page level encryption permits equality searches and range searches? Intuitively it would seem that these searches would require every page to be decrypted to access the column data for each record... unless a proxy Index is used as suggested here