Hello,
my rails application generates lots of small sqlite databases using DataMapper. After data saved, .sqlite-file must be uploaded on a remote server and destroyed locally.
My question is how to make DataMapper close .sqlite db connection and free repo’s memory? Application should generate many databases, so it’s important to save server resources.
Only way I googled is
DataObjects::Pooling.pools.each do {|pool| pool.dispose}
which is totally unacceptable for me I think because it seems to be closing all DataMapper connections, however few databases can be generated simultaneously and I want to destroy DataMapper’s repository too.
Sorry for my English.
Similar:
- Connection Pooling Not working in .Net SQL Server 2008 I’m testing out my application with the hopes of migrating to SQL Server 2008 (From 200). In the SQL Server profiler, I’m seeing Audit Login...
- How do I create an Internal Maven Repository with JBOSS? Hello, Right now I have a JBOSS application server and I want to setup an internal maven2 repository. I want the repository to be located...
- Mercurial, do I need a server for team-work or can I just create a repository on a network share? If I want to set up a smallish Mercurial repository for some internal work among a few developers, can I just navigate to a network...
- CSV to DataMapper Import This is probably very simple, but I’m quite new to ruby and active record. I’ve got a CSV dump of a database which I’m trying...
- Where should I put my svn repository? I am trying to setup a testing server for web development. I have never done this before nor have I ever used svn before. When...
Tags: databases, memory, pool, pools, remote server, repository database, server resources, sqlite