• Created by Unknown User (francisdb), last updated on May 18, 2010 2 minute read

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Is DBDatabase (and related DBTable, DBColumn) thread-safe?

We use empire-db a lot in Web applications which of course use mutlithreaded requests. Normally the data model definition is static i.e. once it is set up, it is not changing and thus accessing it from multiple threads is not a problem. All stateful objects used to access and manipulate data such as DBRecord and DBReader are allocated on a per thread basis. However, if you plan to make dynamic changes to your data model at runtime you will have to make sure that these changes are thread-safe. This must be done at application level.

Should DBDatabase be reopened on every connection or it is enough to open it only once?

The conneciton used when opening the database is not stored with the database. It's purpose is soley to allow the driver to perform intialization functions and may not be used at all. Hence the conneciton may even be null, when opening the database. The open function on the database must only be called once in order to attach the driver. You may then use as many connections as you want - everytime a connection is needed you must supply it with the API call.
In our (web-)projects we usually obtain a connection from a connection pool managed by the application server on a per request basis.

See these projects for more info about connection pools:

Do you have a Scala integration module.

None of us has experience with Scala, but feel free to contribute. This blog post might also help as it points to a project that integrates Scala and empire-db: http://www.acooke.org/cute/UsingScala0.html

  • No labels