On 30 Jun 2011, at 14:13, Simon Slavin wrote:
>
> On 30 Jun 2011, at 8:06pm, Simon Gornall wrote:
>
>> So, the goal is to maximise the number of times the 3rd-pass style can be
>> what is actually being used. At the moment, if an entity gets *any* write
>> operati
On 30 Jun 2011, at 11:42, Simon Slavin wrote:
>
> On 30 Jun 2011, at 7:28pm, Simon Gornall wrote:
>
>> I don't care if an update is made to the *value* of 'otherColumnName'. I
>> only care if the set-of-objects-that-would-be-returned could differ, not the
>>
On 30 Jun 2011, at 11:06, Igor Tandetnik wrote:
> On 6/30/2011 1:43 PM, Simon Gornall wrote:
>> Well, perhaps I'm missing something, but if the statement for which I'm
>> caching results was something like
>>
>> SELECT * FROM tableName WHERE columnName = zzz;
&g
On 30 Jun 2011, at 10:28, Igor Tandetnik wrote:
> On 6/30/2011 1:15 PM, Simon Gornall wrote:
>> Is it possible to get the columns operated on by a WHERE clause from the
>> sqlite3_stmt once it's been prepared ?
>>
>> I looked at the sqlite3_set_authorizer,
Hi there,
Is it possible to get the columns operated on by a WHERE clause from the
sqlite3_stmt once it's been prepared ?
I'm trying to intelligently invalidate cached results after a database UPDATE,
where the results are cached by query. One of the ways the query can be
instantiated is
I wrote a simple client/server SQLite implementation a while ago - the
tarball is at http://blog.gornall.net/assets/sqld.tar.bz2 though the
network-connection to the server is a bit flaky at the moment... It's
freeware, and comes with (C) server and (Objective C) client code.
You'll need
6 matches
Mail list logo
