On 1/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Thoughts anyone? Are there less drastic measures that might
be taken to prevent this kind of abuse?
A couple of people here mentioned CAPTCHA's. This is sort of the standard
for preventing automated abuse (intentional or
On 1/14/07, Dan Kennedy <[EMAIL PROTECTED]> wrote:
So you're right, when you use shared-cache mode there is less
concurrency in some circumstances.
Thanks for your confirmation and additional comments on the situation! It's
good to know that I'm interpreting the source correctly at least.
Hey folks...
I have a situation that caused me a little head-scratching and I'm wondering
if it's intended behavior or not.
I'm running a server thread (roughly based on test_server.c in the distro)
on top of the 3.3.6 library. The effectve call sequence in question (all
from one thread) looks
On 1/12/07, Ken <[EMAIL PROTECTED]> wrote:
If it is a replacement for fopen, then why does it perform locking at all?
Since sqlite has implemented threading and multiple connections, then the
next logical step in its evoloution is to enable advanced locking techniques
for even greater degrees
On 1/8/07, Ken <[EMAIL PROTECTED]> wrote:
You could always implement a sqlite3_open call and store it in the g
variable, and close it when the server quits.
Thanks for your response, Ken. I'm not sure I've explained myself
properly. It's not that I'm calling sqlite3_enable_shared_cache()
> "It is built in" - does it mean that SQLite is wrraped by standard
> Symbian DBMS API or I need to use some other library in mmp file?
> What to You mean by "recent versions of SymbianOS" - it Symbian 8.0
> FP3/FP2 or Symbian 9.1?
Here's a PDF presentation about it...
6 matches
Mail list logo