Thanks Alessandro.

So the approach where we open the db with ":memory:" keyword does not
provide durability .
Only by increasing the cache size can we make db act as an inmemory db with
durablity. That's the conclusion right ?

Thanks
Prakash

On Fri, Oct 17, 2014 at 2:53 PM, Alessandro Marzocchi <
alessandro.marzoc...@gmail.com> wrote:

> From memsql site:
> These features can be tuned all the way from synchronous durability (every
> write transaction is recorded on disk before the query completes) to purely
> in-memory durability (maximum sustained throughput on writes).
>
> From sqlite website:
> The MEMORY journaling mode stores the rollback journal in volatile RAM.
> This saves disk I/O but at the expense of database safety and integrity. If
> the application using SQLite crashes in the middle of a transaction when
> the MEMORY journaling mode is set, then the database file will very likely
> go corrupt. So you can go all the ways from no acid (data and journal in
> ram), to aci database (syncronous=normal) to fully acid. If you increase
> cache size enough you'll have the same as a "in memory" database
> Il 17/ott/2014 14:15 "Prakash Premkumar" <prakash.p...@gmail.com> ha
> scritto:
>
> > Hi,
> > Let's take the case of MemSQL for example. It is an in memory database
> and
> > it supports durability:
> > Link : http://developers.memsql.com/docs/3.1/faq.html#c3-q1
> >
> > And Oracle's In memory db TimesTen also provide durability:
> > Link :
> >
> >
> http://docs.oracle.com/cd/E21901_01/doc/timesten.1122/e21631/overview.htm#TTCIN129
> >
> > Does sqlite's in memory db have this feature ?
> >
> > Thanks
> > Prakash
> >
> > On Fri, Oct 17, 2014 at 11:54 AM, Prakash Premkumar <
> > prakash.p...@gmail.com>
> > wrote:
> >
> > > Is features like WAL (https://www.sqlite.org/wal.html) not available
> for
> > > in memory databases ?
> > >
> > > Thanks
> > > Prakash
> > >
> > > On Fri, Oct 17, 2014 at 11:23 AM, Alessandro Marzocchi <
> > > alessandro.marzoc...@gmail.com> wrote:
> > >
> > >> Today, random-access memory takes the form of integrated circuits
> > >> <http://en.m.wikipedia.org/wiki/Integrated_circuit>. RAM is normally
> > >> associated with volatile <
> > http://en.m.wikipedia.org/wiki/Volatile_memory>
> > >> types
> > >> of memory (such as DRAM <http://en.m.wikipedia.org/wiki/DRAM> memory
> > >> modules
> > >> <http://en.m.wikipedia.org/wiki/DIMM>), where stored information is
> > lost
> > >> if
> > >> the power is removed, although many efforts have been made to develop
> > >> non-volatile RAM chips.
> > >>
> > >> Source: Wikipedia
> > >> Il 17/ott/2014 11:48 "Prakash Premkumar" <prakash.p...@gmail.com> ha
> > >> scritto:
> > >>
> > >> > Hi,
> > >> > Does in memory database in sqlite have journal files associated with
> > it
> > >> ?
> > >> > If there's a system failure before an in memory database is backed
> up
> > ?
> > >> > Will there be data loss ? Or Can you kindly tell me how sqlite
> handles
> > >> this
> > >> > ?
> > >> >
> > >> >
> > >> > Thanks
> > >> > Prakash
> > >> > _______________________________________________
> > >> > sqlite-users mailing list
> > >> > sqlite-users@sqlite.org
> > >> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> > >> >
> > >> _______________________________________________
> > >> sqlite-users mailing list
> > >> sqlite-users@sqlite.org
> > >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> > >>
> > >
> > >
> > _______________________________________________
> > sqlite-users mailing list
> > sqlite-users@sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to