Remove MySQL support of constraint (has it skips it silently) and use double instead of float

[yangoon1, 2010-03-10 17:51:33]

sorry, inline comments atm not working for me:

* MySQL doesn't support constraint but Tryton tries to handle it but it is not
multi-transactional.

* MySQL doesn't support constraint on multi-transactional level (as handled by
Tryton).

[ced, 2010-03-10 18:09:56]

On 2010/03/10 17:51:33, yangoon wrote:
> sorry, inline comments atm not working for me:
> 
> * MySQL doesn't support constraint but Tryton tries to handle it but it is not
> multi-transactional.
> 
> * MySQL doesn't support constraint on multi-transactional level (as handled by
> Tryton).

Your comment suggest that MySQL support constraint in single transaction which
is not the case.

[bch, 2010-03-11 10:55:06]

On 2010/03/11 10:53:04, ced wrote:
> 

OK for me

[ced, 2010-03-11 11:06:13]

On 2010/03/11 10:55:06, bch wrote:
> On 2010/03/11 10:53:04, ced wrote:
> > 
> 
> OK for me

I will remove the comment because it is only the UNIQUE code that is not
multi-transaction but MySQL supports UNIQUE constraint.

[yangoon1, 2010-03-11 11:19:19]

I wouldn't remove the comment, if this is a drawback for the use of Tryton with
mysql.

MySQL doesn't support multi-transactional UNIQUE constraint.

Better?

[ced, 2010-03-11 11:23:29]

On 2010/03/11 11:19:19, yangoon wrote:
> I wouldn't remove the comment, if this is a drawback for the use of Tryton
with
> mysql.

There is a lot of drawback like this one in Tryton for any database backend and
other stuffs.
We will not document what is missing in each tools. Only the things that we can
not workaround.

> 
> MySQL doesn't support multi-transactional UNIQUE constraint.
> 
> Better?

MySQL supports multi-transactional UNIQUE constraint. It is CHECK constraint
that is not supported and this doesn't require multi-transactional behavior.