Re: [sqlite] in-memory database concept

2009-11-05 Thread Stephan Wehner
On Wed, Nov 4, 2009 at 4:57 AM, Serdar Genc  wrote:
> Yes I am aware of that but I need to access an in-memory database from two
> processes which were written in Java and C++.
> I am just looking for a way to do so..

Hey Serdar,

do you have any update on this ? I found your problem quite
interesting, although also difficult.

Stephan

> On Wed, Nov 4, 2009 at 2:50 PM, Jay A. Kreibich  wrote:
>
>> On Wed, Nov 04, 2009 at 10:27:57AM +0200, Serdar Genc scratched on the
>> wall:
>>
>> > But when I try to do this for in-memory, everything is getting chunky. A
>> new
>> > database is being created in memory for every attempt to open
>> > database in memory. Now I am trying to switch the database handler
>> between
>> > C++ and Java. It requires some efforts.
>>
>>   Yes, that's how it is supposed to work.  A ":memory:" database can
>>  only be accessed by the database handle that created it.  They're not
>>  designed to be shared.
>>
>>  http://www.sqlite.org/inmemorydb.html
>>
>>   -j
>>
>> --
>> Jay A. Kreibich < J A Y  @  K R E I B I.C H >
>>
>> "Our opponent is an alien starship packed with atomic bombs.  We have
>>  a protractor."   "I'll go home and see if I can scrounge up a ruler
>>  and a piece of string."  --from Anathem by Neal Stephenson
>> ___
>> 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
>



-- 
Stephan Wehner

-> http://stephan.sugarmotor.org (blog and homepage)
-> http://loggingit.com
-> http://www.thrackle.org
-> http://www.buckmaster.ca
-> http://www.trafficlife.com
-> http://stephansmap.org -- http://blog.stephansmap.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] in-memory database concept

2009-11-04 Thread O'Neill, Owen


If that's really what you want to do then I think something along the
lines of keeping the DB in the C++ program and then using a named pipe
or socket to do the inter-processes communication between the java and
C++ programs is the way to go. - or some CORBA/SOAP like wrapper to do
the remote function call between the two processes. (at the end of the
day both CORBA and SOAP are RPC over a socket-ed connection using XML or
similar to serialise the function call / return over the socket with
varying degrees of assistance from the supporting framework).

Using JNI to call to/from the C++ is probably not the best route to
achieve what you want since you want two separate processes accessing
the same in-memory database. (and it has a reputation for being quite
painful to implement)

Essentially you're wanting to mimic a client - server situation, so
maybe the way to go is take once of these client server
implementations...
http://www.sqlite.org/cvstrac/wiki?p=SqliteNetwork

and create/ modify a SQLite JDBC driver so that speaks the same protocol
as one of the above ?. (he says in blissful ignorance of any of the
implementation details of any of the sqlite JDBC drivers so I don't know
what the practicalities are.)

cheers
Owen





-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Serdar Genc
Sent: Wednesday, November 04, 2009 12:57 PM
To: j...@kreibi.ch; General Discussion of SQLite Database
Subject: Re: [sqlite] in-memory database concept

Yes I am aware of that but I need to access an in-memory database from
two
processes which were written in Java and C++.
I am just looking for a way to do so..

On Wed, Nov 4, 2009 at 2:50 PM, Jay A. Kreibich  wrote:

> On Wed, Nov 04, 2009 at 10:27:57AM +0200, Serdar Genc scratched on the
> wall:
>
> > But when I try to do this for in-memory, everything is getting
chunky. A
> new
> > database is being created in memory for every attempt to open
> > database in memory. Now I am trying to switch the database handler
> between
> > C++ and Java. It requires some efforts.
>
>   Yes, that's how it is supposed to work.  A ":memory:" database can
>  only be accessed by the database handle that created it.  They're not
>  designed to be shared.
>
>  http://www.sqlite.org/inmemorydb.html
>
>   -j
>
> --
> Jay A. Kreibich < J A Y  @  K R E I B I.C H >
>
> "Our opponent is an alien starship packed with atomic bombs.  We have
>  a protractor."   "I'll go home and see if I can scrounge up a ruler
>  and a piece of string."  --from Anathem by Neal Stephenson
> ___
> 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


Re: [sqlite] in-memory database concept

2009-11-04 Thread Serdar Genc
Yes I am aware of that but I need to access an in-memory database from two
processes which were written in Java and C++.
I am just looking for a way to do so..

On Wed, Nov 4, 2009 at 2:50 PM, Jay A. Kreibich  wrote:

> On Wed, Nov 04, 2009 at 10:27:57AM +0200, Serdar Genc scratched on the
> wall:
>
> > But when I try to do this for in-memory, everything is getting chunky. A
> new
> > database is being created in memory for every attempt to open
> > database in memory. Now I am trying to switch the database handler
> between
> > C++ and Java. It requires some efforts.
>
>   Yes, that's how it is supposed to work.  A ":memory:" database can
>  only be accessed by the database handle that created it.  They're not
>  designed to be shared.
>
>  http://www.sqlite.org/inmemorydb.html
>
>   -j
>
> --
> Jay A. Kreibich < J A Y  @  K R E I B I.C H >
>
> "Our opponent is an alien starship packed with atomic bombs.  We have
>  a protractor."   "I'll go home and see if I can scrounge up a ruler
>  and a piece of string."  --from Anathem by Neal Stephenson
> ___
> 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


Re: [sqlite] in-memory database concept

2009-11-04 Thread Jay A. Kreibich
On Wed, Nov 04, 2009 at 10:27:57AM +0200, Serdar Genc scratched on the wall:

> But when I try to do this for in-memory, everything is getting chunky. A new
> database is being created in memory for every attempt to open
> database in memory. Now I am trying to switch the database handler between
> C++ and Java. It requires some efforts.

  Yes, that's how it is supposed to work.  A ":memory:" database can
  only be accessed by the database handle that created it.  They're not
  designed to be shared.
 
  http://www.sqlite.org/inmemorydb.html

   -j

-- 
Jay A. Kreibich < J A Y  @  K R E I B I.C H >

"Our opponent is an alien starship packed with atomic bombs.  We have
 a protractor."   "I'll go home and see if I can scrounge up a ruler
 and a piece of string."  --from Anathem by Neal Stephenson
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] in-memory database concept

2009-11-04 Thread Serdar Genc
I also tried it.. The result is just like the same with /tmp

Total time to insert 100.000 data into database:

ramdisk: 69860 ms
memory: 9606 ms

Serdar

On Wed, Nov 4, 2009 at 12:14 PM, Abel, John  wrote:

> Hi Serdar,
>
> For Solaris, you need:
>
>ramdiskadm -a mydisk 2m
>newfs /dev/rramdisk/mydisk
>  mkdir /mnt/ramDisk
>  mount /dev/ramdisk/mydisk /mnt/ramDisk
>
>
> John
>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Serdar Genc
> Sent: 04 November 2009 09:13
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] in-memory database concept
>
> Yes you are right about it but when I tried to mount a place as tmpfs,
> its
> type seemed swap just like /tmp.
> The speed seems to be same with /tmp. What I need to increase the speed
> for
> /tmp or another solution for
> in-memory database.
>
> Serdar
>
> On Wed, Nov 4, 2009 at 10:56 AM, Stephan Wehner
> wrote:
>
> > On Wed, Nov 4, 2009 at 12:51 AM, Serdar Genc 
> > wrote:
> > > The OS that I am implementing this is SunOS and I have already tried
> > doing
> > > it by creating the file in /tmp but
> > > but because of file I/O operations to reach /tmp. The speed of
> sqlite is
> > > significantly slow (memory is 5 times faster than file system).
> Speed of
> > > Sqlite is important for me. That's why I still working on the memory
> > issue.
> > >
> >
> > Hi there,
> >
> > /tmp is not the same as tmpfs -- tmpfs is a file system that stores
> > files in RAM, but looks otherwise like any other file system.
> >
> > On SunOS it should be straightforward; that wiki page says "SunOS, and
> > later Solaris, include probably the earliest implementations of
> > tmpfs".
> >
> > Stephan
> >
> > > Thanks for the answer,
> > > Serdar Genc
> > >
> > > On Wed, Nov 4, 2009 at 10:45 AM, Stephan Wehner
>  > >wrote:
> > >
> > >> On Wed, Nov 4, 2009 at 12:27 AM, Serdar Genc
> 
> > >> wrote:
> > >> > Hello everyone,
> > >> >
> > >> > I have a little bit problem about in-memory database feature of
> > SQLite. I
> > >> > would like to use two programming languages in my application .
> > >> > These languages will be Java and C++. I would like to reach the
> same
> > >> > database in memory by using both. I used Xerial for JDBC for
> Java.
> > >> > Everything seems fine if I am using a regular file on harddrive.
> I can
> > >> write
> > >> > data from C++ process and read these data from Java.
> > >> > But when I try to do this for in-memory, everything is getting
> chunky.
> > A
> > >> new
> > >> > database is being created in memory for every attempt to open
> > >> > database in memory. Now I am trying to switch the database
> handler
> > >> between
> > >> > C++ and Java. It requires some efforts.
> > >> >
> > >> > What I want to try to reach the same database in memory from two
> > threads
> > >> or
> > >> > processes and these would be in different programming languages.
> > >> > Any different idea how to implement this is appreciated..
> > >>
> > >> Can you use a RAM based file system?
> > >>
> > >>  http://en.wikipedia.org/wiki/Tmpfs
> > >>
> > >> Stephan
> > >>
> > >> > Thanks in advance,
> > >> > Serdar Genc
> > >> > ___
> > >> > sqlite-users mailing list
> > >> > sqlite-users@sqlite.org
> > >> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Stephan Wehner
> > >>
> > >> -> http://stephan.sugarmotor.org (blog and homepage)
> > >> -> http://loggingit.com
> > >> -> http://www.thrackle.org
> > >> -> http://www.buckmaster.ca
> > >> -> http://www.trafficlife.com
> > >> -> http://stephansmap.org -- http://blog.stephansmap.org
> > >> ___
> > >> sqlite-users mailing list
> > >> sqlite-users@sqlite.org
> > >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] in-memory database concept

2009-11-04 Thread Abel, John
Hi Serdar,

For Solaris, you need:

ramdiskadm -a mydisk 2m
newfs /dev/rramdisk/mydisk
  mkdir /mnt/ramDisk
  mount /dev/ramdisk/mydisk /mnt/ramDisk


John

-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Serdar Genc
Sent: 04 November 2009 09:13
To: General Discussion of SQLite Database
Subject: Re: [sqlite] in-memory database concept

Yes you are right about it but when I tried to mount a place as tmpfs,
its
type seemed swap just like /tmp.
The speed seems to be same with /tmp. What I need to increase the speed
for
/tmp or another solution for
in-memory database.

Serdar

On Wed, Nov 4, 2009 at 10:56 AM, Stephan Wehner
wrote:

> On Wed, Nov 4, 2009 at 12:51 AM, Serdar Genc 
> wrote:
> > The OS that I am implementing this is SunOS and I have already tried
> doing
> > it by creating the file in /tmp but
> > but because of file I/O operations to reach /tmp. The speed of
sqlite is
> > significantly slow (memory is 5 times faster than file system).
Speed of
> > Sqlite is important for me. That's why I still working on the memory
> issue.
> >
>
> Hi there,
>
> /tmp is not the same as tmpfs -- tmpfs is a file system that stores
> files in RAM, but looks otherwise like any other file system.
>
> On SunOS it should be straightforward; that wiki page says "SunOS, and
> later Solaris, include probably the earliest implementations of
> tmpfs".
>
> Stephan
>
> > Thanks for the answer,
> > Serdar Genc
> >
> > On Wed, Nov 4, 2009 at 10:45 AM, Stephan Wehner
 >wrote:
> >
> >> On Wed, Nov 4, 2009 at 12:27 AM, Serdar Genc

> >> wrote:
> >> > Hello everyone,
> >> >
> >> > I have a little bit problem about in-memory database feature of
> SQLite. I
> >> > would like to use two programming languages in my application .
> >> > These languages will be Java and C++. I would like to reach the
same
> >> > database in memory by using both. I used Xerial for JDBC for
Java.
> >> > Everything seems fine if I am using a regular file on harddrive.
I can
> >> write
> >> > data from C++ process and read these data from Java.
> >> > But when I try to do this for in-memory, everything is getting
chunky.
> A
> >> new
> >> > database is being created in memory for every attempt to open
> >> > database in memory. Now I am trying to switch the database
handler
> >> between
> >> > C++ and Java. It requires some efforts.
> >> >
> >> > What I want to try to reach the same database in memory from two
> threads
> >> or
> >> > processes and these would be in different programming languages.
> >> > Any different idea how to implement this is appreciated..
> >>
> >> Can you use a RAM based file system?
> >>
> >>  http://en.wikipedia.org/wiki/Tmpfs
> >>
> >> Stephan
> >>
> >> > Thanks in advance,
> >> > Serdar Genc
> >> > ___
> >> > sqlite-users mailing list
> >> > sqlite-users@sqlite.org
> >> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >> >
> >>
> >>
> >>
> >> --
> >> Stephan Wehner
> >>
> >> -> http://stephan.sugarmotor.org (blog and homepage)
> >> -> http://loggingit.com
> >> -> http://www.thrackle.org
> >> -> http://www.buckmaster.ca
> >> -> http://www.trafficlife.com
> >> -> http://stephansmap.org -- http://blog.stephansmap.org
> >> ___
> >> 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
> >
>
>
>
> --
> Stephan Wehner
>
> -> http://stephan.sugarmotor.org (blog and homepage)
> -> http://loggingit.com
> -> http://www.thrackle.org
> -> http://www.buckmaster.ca
> -> http://www.trafficlife.com
> -> http://stephansmap.org -- http://blog.stephansmap.org
> ___
> 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


This message has been scanned for viruses by BlackSpider MailControl - 
www.blackspider.com

Balfour Beatty Utility Solutions Limited

Registered Office 01062438: Park Square, Newton Chambers Road, Thorncliffe 
Park, Chapeltown, Sheffield, S35 2PH.

Registered Office 02067112: West Service Road, Raynesway, Derby, DE21 7BG.

An agent of Balfour Beatty Group Limited.
Registered Office 101073: 130 Wilton Road, London, SW1V 1LQ.

Place of Registration: Registered in England and Wales

© 2007 Balfour Beatty Power Networks Ltd. trading as Balfour Beatty Utility 
Solutions

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] in-memory database concept

2009-11-04 Thread Serdar Genc
Yes you are right about it but when I tried to mount a place as tmpfs, its
type seemed swap just like /tmp.
The speed seems to be same with /tmp. What I need to increase the speed for
/tmp or another solution for
in-memory database.

Serdar

On Wed, Nov 4, 2009 at 10:56 AM, Stephan Wehner wrote:

> On Wed, Nov 4, 2009 at 12:51 AM, Serdar Genc 
> wrote:
> > The OS that I am implementing this is SunOS and I have already tried
> doing
> > it by creating the file in /tmp but
> > but because of file I/O operations to reach /tmp. The speed of sqlite is
> > significantly slow (memory is 5 times faster than file system). Speed of
> > Sqlite is important for me. That's why I still working on the memory
> issue.
> >
>
> Hi there,
>
> /tmp is not the same as tmpfs -- tmpfs is a file system that stores
> files in RAM, but looks otherwise like any other file system.
>
> On SunOS it should be straightforward; that wiki page says "SunOS, and
> later Solaris, include probably the earliest implementations of
> tmpfs".
>
> Stephan
>
> > Thanks for the answer,
> > Serdar Genc
> >
> > On Wed, Nov 4, 2009 at 10:45 AM, Stephan Wehner  >wrote:
> >
> >> On Wed, Nov 4, 2009 at 12:27 AM, Serdar Genc 
> >> wrote:
> >> > Hello everyone,
> >> >
> >> > I have a little bit problem about in-memory database feature of
> SQLite. I
> >> > would like to use two programming languages in my application .
> >> > These languages will be Java and C++. I would like to reach the same
> >> > database in memory by using both. I used Xerial for JDBC for Java.
> >> > Everything seems fine if I am using a regular file on harddrive. I can
> >> write
> >> > data from C++ process and read these data from Java.
> >> > But when I try to do this for in-memory, everything is getting chunky.
> A
> >> new
> >> > database is being created in memory for every attempt to open
> >> > database in memory. Now I am trying to switch the database handler
> >> between
> >> > C++ and Java. It requires some efforts.
> >> >
> >> > What I want to try to reach the same database in memory from two
> threads
> >> or
> >> > processes and these would be in different programming languages.
> >> > Any different idea how to implement this is appreciated..
> >>
> >> Can you use a RAM based file system?
> >>
> >>  http://en.wikipedia.org/wiki/Tmpfs
> >>
> >> Stephan
> >>
> >> > Thanks in advance,
> >> > Serdar Genc
> >> > ___
> >> > sqlite-users mailing list
> >> > sqlite-users@sqlite.org
> >> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >> >
> >>
> >>
> >>
> >> --
> >> Stephan Wehner
> >>
> >> -> http://stephan.sugarmotor.org (blog and homepage)
> >> -> http://loggingit.com
> >> -> http://www.thrackle.org
> >> -> http://www.buckmaster.ca
> >> -> http://www.trafficlife.com
> >> -> http://stephansmap.org -- http://blog.stephansmap.org
> >> ___
> >> 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
> >
>
>
>
> --
> Stephan Wehner
>
> -> http://stephan.sugarmotor.org (blog and homepage)
> -> http://loggingit.com
> -> http://www.thrackle.org
> -> http://www.buckmaster.ca
> -> http://www.trafficlife.com
> -> http://stephansmap.org -- http://blog.stephansmap.org
> ___
> 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


Re: [sqlite] in-memory database concept

2009-11-04 Thread Stephan Wehner
On Wed, Nov 4, 2009 at 12:51 AM, Serdar Genc  wrote:
> The OS that I am implementing this is SunOS and I have already tried doing
> it by creating the file in /tmp but
> but because of file I/O operations to reach /tmp. The speed of sqlite is
> significantly slow (memory is 5 times faster than file system). Speed of
> Sqlite is important for me. That's why I still working on the memory issue.
>

Hi there,

/tmp is not the same as tmpfs -- tmpfs is a file system that stores
files in RAM, but looks otherwise like any other file system.

On SunOS it should be straightforward; that wiki page says "SunOS, and
later Solaris, include probably the earliest implementations of
tmpfs".

Stephan

> Thanks for the answer,
> Serdar Genc
>
> On Wed, Nov 4, 2009 at 10:45 AM, Stephan Wehner 
> wrote:
>
>> On Wed, Nov 4, 2009 at 12:27 AM, Serdar Genc 
>> wrote:
>> > Hello everyone,
>> >
>> > I have a little bit problem about in-memory database feature of SQLite. I
>> > would like to use two programming languages in my application .
>> > These languages will be Java and C++. I would like to reach the same
>> > database in memory by using both. I used Xerial for JDBC for Java.
>> > Everything seems fine if I am using a regular file on harddrive. I can
>> write
>> > data from C++ process and read these data from Java.
>> > But when I try to do this for in-memory, everything is getting chunky. A
>> new
>> > database is being created in memory for every attempt to open
>> > database in memory. Now I am trying to switch the database handler
>> between
>> > C++ and Java. It requires some efforts.
>> >
>> > What I want to try to reach the same database in memory from two threads
>> or
>> > processes and these would be in different programming languages.
>> > Any different idea how to implement this is appreciated..
>>
>> Can you use a RAM based file system?
>>
>>  http://en.wikipedia.org/wiki/Tmpfs
>>
>> Stephan
>>
>> > Thanks in advance,
>> > Serdar Genc
>> > ___
>> > sqlite-users mailing list
>> > sqlite-users@sqlite.org
>> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>> >
>>
>>
>>
>> --
>> Stephan Wehner
>>
>> -> http://stephan.sugarmotor.org (blog and homepage)
>> -> http://loggingit.com
>> -> http://www.thrackle.org
>> -> http://www.buckmaster.ca
>> -> http://www.trafficlife.com
>> -> http://stephansmap.org -- http://blog.stephansmap.org
>> ___
>> 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
>



-- 
Stephan Wehner

-> http://stephan.sugarmotor.org (blog and homepage)
-> http://loggingit.com
-> http://www.thrackle.org
-> http://www.buckmaster.ca
-> http://www.trafficlife.com
-> http://stephansmap.org -- http://blog.stephansmap.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] in-memory database concept

2009-11-04 Thread Serdar Genc
The OS that I am implementing this is SunOS and I have already tried doing
it by creating the file in /tmp but
but because of file I/O operations to reach /tmp. The speed of sqlite is
significantly slow (memory is 5 times faster than file system). Speed of
Sqlite is important for me. That's why I still working on the memory issue.

Thanks for the answer,
Serdar Genc

On Wed, Nov 4, 2009 at 10:45 AM, Stephan Wehner wrote:

> On Wed, Nov 4, 2009 at 12:27 AM, Serdar Genc 
> wrote:
> > Hello everyone,
> >
> > I have a little bit problem about in-memory database feature of SQLite. I
> > would like to use two programming languages in my application .
> > These languages will be Java and C++. I would like to reach the same
> > database in memory by using both. I used Xerial for JDBC for Java.
> > Everything seems fine if I am using a regular file on harddrive. I can
> write
> > data from C++ process and read these data from Java.
> > But when I try to do this for in-memory, everything is getting chunky. A
> new
> > database is being created in memory for every attempt to open
> > database in memory. Now I am trying to switch the database handler
> between
> > C++ and Java. It requires some efforts.
> >
> > What I want to try to reach the same database in memory from two threads
> or
> > processes and these would be in different programming languages.
> > Any different idea how to implement this is appreciated..
>
> Can you use a RAM based file system?
>
>  http://en.wikipedia.org/wiki/Tmpfs
>
> Stephan
>
> > Thanks in advance,
> > Serdar Genc
> > ___
> > sqlite-users mailing list
> > sqlite-users@sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >
>
>
>
> --
> Stephan Wehner
>
> -> http://stephan.sugarmotor.org (blog and homepage)
> -> http://loggingit.com
> -> http://www.thrackle.org
> -> http://www.buckmaster.ca
> -> http://www.trafficlife.com
> -> http://stephansmap.org -- http://blog.stephansmap.org
> ___
> 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


Re: [sqlite] in-memory database concept

2009-11-04 Thread Stephan Wehner
On Wed, Nov 4, 2009 at 12:27 AM, Serdar Genc  wrote:
> Hello everyone,
>
> I have a little bit problem about in-memory database feature of SQLite. I
> would like to use two programming languages in my application .
> These languages will be Java and C++. I would like to reach the same
> database in memory by using both. I used Xerial for JDBC for Java.
> Everything seems fine if I am using a regular file on harddrive. I can write
> data from C++ process and read these data from Java.
> But when I try to do this for in-memory, everything is getting chunky. A new
> database is being created in memory for every attempt to open
> database in memory. Now I am trying to switch the database handler between
> C++ and Java. It requires some efforts.
>
> What I want to try to reach the same database in memory from two threads or
> processes and these would be in different programming languages.
> Any different idea how to implement this is appreciated..

Can you use a RAM based file system?

  http://en.wikipedia.org/wiki/Tmpfs

Stephan

> Thanks in advance,
> Serdar Genc
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Stephan Wehner

-> http://stephan.sugarmotor.org (blog and homepage)
-> http://loggingit.com
-> http://www.thrackle.org
-> http://www.buckmaster.ca
-> http://www.trafficlife.com
-> http://stephansmap.org -- http://blog.stephansmap.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users