Jim Dodgen <[EMAIL PROTECTED]> wrote:
> one simple trick I first started using with oracle and also use with
> sqlite is to do the following on the where clause
> for numerics
> where filda = fldb+0
>
> for strings
>
> where flda = fldb||""
>
> this would cause a index on fldb to be ignored
one simple trick I first started using with oracle and also use with
sqlite is to do the following on the where clause
for numerics
where filda = fldb+0
for strings
where flda = fldb||""
this would cause a index on fldb to be ignored during optimization
Jim
Dennis Cote wrote:
On 2/18/06,
Op zondag 19 februari 2006 13:23, schreef Nemanja Corlija:
> On 2/19/06, SanjayK <[EMAIL PROTECTED]> wrote:
> > I am using a virtual tree control to display columns dynamically when
> > needed from the sqlite database. While it works ok for display purposes,
> > in certain other operations, I need
On 2/19/06, SanjayK <[EMAIL PROTECTED]> wrote:
>
> I am using a virtual tree control to display columns dynamically when needed
> from the sqlite database. While it works ok for display purposes, in certain
> other operations, I need to improve the speed. I found that the new sqlite
> random
On 2/18/06, SanjayK <[EMAIL PROTECTED]> wrote:
>
>
> I am using a virtual tree control to display columns dynamically when
> needed
> from the sqlite database. While it works ok for display purposes, in
> certain
> other operations, I need to improve the speed. I found that the new sqlite
> random
I am using a virtual tree control to display columns dynamically when needed
from the sqlite database. While it works ok for display purposes, in certain
other operations, I need to improve the speed. I found that the new sqlite
random access (even with prepared/transaction) approach is about 15
6 matches
Mail list logo
