Technical mailing list archives

Re: About MySQL support

Camptocamp France SAS, Alexandre Fayolle - Camptocamp
- 02/09/2016 08:52:53
On 09/02/2016 10:42, Luca Vercelli wrote:
> Thank you all for your opinions.
> The scenario I have in mind is the following: a company has "its own
> datacenter" (tipically SQL server), with good technicians and good
> backups already configured, and they don't want even ear about saving
> data into a different database.
> Personally, I did't imagine that this modification were such a big
> effort. I thought that it were possible, for example, let Odoo to
> communicate to postgresql through an intermediate level, a "common
> driver interface" [1].

Connecting to the database is one thing, and this is achieved by the
Python DB API. What this does not achieve is abstraction of SQL
specificities, especially the SQL extensions from PostgreSQL which Odoo
uses and which are not supported by other engines (last time I checked,
MSSql did not support OFFSET and LIMIT) or the weird implementations
from other database engines (last time I checked, MSSql still did not
implement UNIQUE index on nullable columns correctly). And I won't even
start on the behavior of VARCHAR without a size, NUMERIC without a size,
and BLOBs.

The net effect is that if your customer insists on having something else
than PostgreSQL, you'll have to either change customer or change product.

Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex