Roger Binns wrote:
>> John Stanton has correctly pointed out that there is a programming model
>> here an application effectively does the cacheing itself by precompiling
>
> statements at startup.
>
> That is not caching and it would be unaffected by any caching scheme.
> sqlite3_finalize
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas E. Fajardo wrote:
> John Stanton has correctly pointed out that there is a programming model here
> an application
> effectively does the cacheing itself by precompiling statements at startup.
> In this situation,
> the proposed cacheing
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Distinguishing between sqlite3_stmts
You make a argument for Bloatware. It is not oersuasive.
JS
Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> John Stanton wrote:
>
>>Perhaps this featr
] Distinguishing between sqlite3_stmts
On Nov 8, 2008, at 3:25 AM, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Douglas E. Fajardo wrote:
>> ( To the 'powers that be'... I wonder if some form of 'cache' for
>> prepared statements might be built in
You make a argument for Bloatware. It is not oersuasive.
JS
Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> John Stanton wrote:
>
>>Perhaps this featrure could be reserved for "Sqlheavy", a replacement
>>for Oracle.
>
>
> Or a #if OMIT_STATEMENT_CACHE like all sorts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Stanton wrote:
> Perhaps this featrure could be reserved for "Sqlheavy", a replacement
> for Oracle.
Or a #if OMIT_STATEMENT_CACHE like all sorts of other functionality that
can be omitted.
> We have actually implemented the cacheing of
Dan wrote:
> On Nov 8, 2008, at 3:25 AM, Roger Binns wrote:
>
>
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>Douglas E. Fajardo wrote:
>>
>>> ( To the 'powers that be'... I wonder if some form of 'cache' for
>>>prepared statements might be built in to the 'sqlite3_prepare*'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan wrote:
>> http://www.sqlite.org/cvstrac/tktview?tn=3483
>
> Are there advantages to implementing this internally instead of
> externally?
Firstly there is an advantage to having a statement cache. I use a
benchmark based on
On Nov 8, 2008, at 3:25 AM, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Douglas E. Fajardo wrote:
>> ( To the 'powers that be'... I wonder if some form of 'cache' for
>> prepared statements might be built in to the 'sqlite3_prepare*'
>> functions as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas E. Fajardo wrote:
>( To the 'powers that be'... I wonder if some form of 'cache' for prepared
> statements might be built in to the 'sqlite3_prepare*' functions as a
> performance enhancement? )
I couldn't find an existing ticket so
Hipp
Sent: Thursday, November 06, 2008 4:54 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Distinguishing between sqlite3_stmts
On Nov 6, 2008, at 7:47 PM, Brown, Daniel wrote:
> Good afternoon list,
>
> Are there any methods for distinguishing between sqlite3_stmt
>
]
[mailto:[EMAIL PROTECTED] On Behalf Of D. Richard Hipp
Sent: Thursday, November 06, 2008 4:54 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Distinguishing between sqlite3_stmts
On Nov 6, 2008, at 7:47 PM, Brown, Daniel wrote:
> Good afternoon list,
>
> Are there an
On Nov 6, 2008, at 7:47 PM, Brown, Daniel wrote:
> Good afternoon list,
>
> Are there any methods for distinguishing between sqlite3_stmt
> structures
> prepared by sqlite3_prepare_v2? I'd like to be able to tell if a
> statement structure has been finalized and then prepared with a
>
Good afternoon list,
Are there any methods for distinguishing between sqlite3_stmt structures
prepared by sqlite3_prepare_v2? I'd like to be able to tell if a
statement structure has been finalized and then prepared with a
different query programmatically. Is there any sort of unique
identifier
14 matches
Mail list logo
