On 17 Jul 2012, at 9:04am, Durga D wrote:
> Hi Simon, what you suggest now? sigle object based or set of connections?
Sorry, I have no experience with what you're doing. I hope someone else can
advise you or you can try out a solution and tell whether it does what you want.
Simon.
__
Hi Simon, what you suggest now? sigle object based or set of connections?
Thanks,
On Mon, Jul 16, 2012 at 6:11 PM, Simon Slavin wrote:
>
> On 16 Jul 2012, at 2:59pm, "Igor Tandetnik" wrote:
>
> > Durga D wrote:
> >> So, I can establish x connections in app initialize time in WAL mode.
> >>
On 16 Jul 2012, at 2:59pm, "Igor Tandetnik" wrote:
> Durga D wrote:
>> So, I can establish x connections in app initialize time in WAL mode.
>> Based on request (read or write), I can pick the connection and serve.
>> Allows only one write at a time.
>
> I'm not sure what you mean by picking
Durga D wrote:
>So, I can establish x connections in app initialize time in WAL mode.
> Based on request (read or write), I can pick the connection and serve.
> Allows only one write at a time.
I'm not sure what you mean by picking a connection based on a request. It's not
connections that a
Hi Michael/Igor,
So, I can establish x connections in app initialize time in WAL mode.
Based on request (read or write), I can pick the connection and serve.
Allows only one write at a time.
Is it correct?
Thanks in advance.
Regards,
On Mon, Jul 16, 2012 at 4:43 PM, Igor Tandetnik
Black, Michael (IS) wrote:
> Ummmare we forgetting about WAL mode?
>
> http://www.sqlite.org/draft/wal.html
>
> "Reading and writing can proceed concurrently."
>
> Not that you can have multiples of each...just one of each.
To be precise, with WAL you can have one writer and multiple reade
t: EXT :Re: [sqlite] set of db connections
On 16 Jul 2012, at 12:09pm, Durga D wrote:
>scenario: while write request is in progress with 100K records
> insertion, new request with reading of 1 records already existing
> records. Here, read request should wait till write reque
Got it. Thank you so much.
On Mon, Jul 16, 2012 at 3:24 PM, Simon Slavin wrote:
>
> On 16 Jul 2012, at 12:09pm, Durga D wrote:
>
> >scenario: while write request is in progress with 100K records
> > insertion, new request with reading of 1 records already existing
> > records. Here, rea
On 16 Jul 2012, at 12:09pm, Durga D wrote:
>scenario: while write request is in progress with 100K records
> insertion, new request with reading of 1 records already existing
> records. Here, read request should wait till write request completes. Is it
> correct?
You are correct. In or
Hi Simon,
I agree with one connection logic.
scenario: while write request is in progress with 100K records
insertion, new request with reading of 1 records already existing
records. Here, read request should wait till write request completes. Is it
correct?
Thanks in advance.
R
On 16 Jul 2012, at 7:50am, Durga D wrote:
>I am developing readers (> 1) and writer(1) application for sqlite3 db.
>
>I would like to maintain set of connections in application
> initialization time. whenever read request comes, serve the request from
> existing connection object like p
Hi all,
I am developing readers (> 1) and writer(1) application for sqlite3 db.
I would like to maintain set of connections in application
initialization time. whenever read request comes, serve the request from
existing connection object like pool.
Here, my doubt is: if app. runs fo
12 matches
Mail list logo
