Doctrine 2 and Concrete table inheritance

I use Doctrine 2 and I’ve read some articles on inheritance strategies’ mapping with ORM.
I’ve seen three main strategies : “Class table inheritance”, “Concrete table inheritance” and “Single table inheritance”.

Doctrine 2 and Concrete table inheritance

I use Doctrine 2 and I’ve read some articles on inheritance strategies’ mapping with ORM.
I’ve seen three main strategies : “Class table inheritance”, “Concrete table inheritance” and “Single table inheritance”.

How far can I drift from my original domain model and still have the benefits of an ORM?

I have the following domain models:

How far can I drift from my original domain model and still have the benefits of an ORM?

I have the following domain models:

Extending database model of ORM in subproject

I have a maven project which contains some entities which are stored in a database. The purpose of this project is to manage personal information, users, locations, etc. This project can work on its own.

Limitations of the Identity Map pattern

After asking about the implementation in Ruby of the Identity Map pattern because the potential memory leak in long running server apps, I am considering my initial concept of that pattern.

Finding a way to simplify complex queries on legacy application

I am working with an existing application built on Rails 3.1/MySql with much of the work taking place in a JavaScript interface, although the actual platforms are not tremendously relevant here, except in that they give context.

Finding a way to simplify complex queries on legacy application

I am working with an existing application built on Rails 3.1/MySql with much of the work taking place in a JavaScript interface, although the actual platforms are not tremendously relevant here, except in that they give context.

Finding a way to simplify complex queries on legacy application

I am working with an existing application built on Rails 3.1/MySql with much of the work taking place in a JavaScript interface, although the actual platforms are not tremendously relevant here, except in that they give context.

Real time middleware system: Direct DB access vs REST API access

I’m developing a complex environment which involves a web application, a mobile app and a real time middleware system which accesses the DB for on-site tag readings. Currently, the web application exposes some services over a REST API, which are accessed by the mobile app to let it perform its business work (in this case, time delay is not critical). However, for my middleware system, I access the DB directly (through a ORM), in order to provide faster responses.