On 24 Mar 18:36, Guillem Barba Domingo wrote:
> El 24/03/2014 14:51, "Cédric Krier" va escriure:
> >
> > On 24 Mar 08:51, Guillem Barba Domingo wrote:
> > > You can achieve what you want with a UNIQUE sql_constraint and with
> _order
> > > property of model.
> >
> > UNIQUE constraints should alway
El 24/03/2014 14:51, "Cédric Krier" va escriure:
>
> On 24 Mar 08:51, Guillem Barba Domingo wrote:
> > You can achieve what you want with a UNIQUE sql_constraint and with
_order
> > property of model.
>
> UNIQUE constraints should always avoided if possible.
Why?
On 24 Mar 08:51, Guillem Barba Domingo wrote:
> You can achieve what you want with a UNIQUE sql_constraint and with _order
> property of model.
UNIQUE constraints should always avoided if possible.
> BUT it will work for the original value, not for translated one.
order on translated value works
Hi Guillem,
Am Montag, 24. März 2014 08:51:06 UTC+1 schrieb Guillem Barba:
>
> > Second thingthe list is unsorted, which makes it hard to maintain.
> As long as the GUI does not offer a sort function on Name, I think the use
> of sorted tables could be an option (TYPE sorted table of...). Do
>
>> Will there be an official 3.0.3 before that?
>
>
Yep, now its there :-)
Thanks
El 21/03/2014 16:20, "Axel Braun" va escriure:
>
> Hi,
>
> while creating product categories I noticed that it is possible to enter
the same category twice. In a large number of product categories this is
easily possible, but should be avoided. I assume it is stored not with the
name, but with an
