openerp-expert-framework team mailing list archive
-
openerp-expert-framework team
-
Mailing list archive
-
Message #00120
Re: Errors handling
-
To:
openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
-
From:
Ferdinand Gassauer <office@xxxxxxxxxx>
-
Date:
Sun, 24 Jan 2010 15:49:59 +0100
-
In-reply-to:
<1264335925.5923.31.camel@sirah>
-
Organization:
ChriCar Beteiligungss- und Beratungs- GmbH
-
User-agent:
KMail/1.12.4 (Linux/2.6.31.8-0.1-desktop; KDE/4.3.4; x86_64; ; )
> Hello Experts,
>
> one of the most important issues, in our customers' opinion, is the
> openobject's errors handling.
>
> Let me give you an example.
>
> Create a category, create a product and then put this product inside the
> previously created category.
> Now, delete that product and try to delete the category.
>
> OpenObject throws an exception because there is a product template still
> associated with that category
>
> -----------------------------------------------------------------------
> Integrity Error
>
> null value in column "categ_id" violates not-null constraint
> CONTEXT: SQL statement "UPDATE ONLY "public"."product_template" SET
> "categ_id" = NULL WHERE $1 OPERATOR(pg_catalog.=) "categ_id""
> -----------------------------------------------------------------------
>
> In this case a user has to ask a technician to solve the problem, mainly
> because he cannot understand the error message.
>
> Instead of that message, openobject should say something like "In order
> to delete this category you must first delete every related products.
> Click here to view the list of related objects".
+1
IMHO it would also be helpful to gather the rev id of server addons etc
currently only the rev of the client is given in the error message
--
regards
Ferdinand Gassauer
ChriCar Beteiligungs- und Beratungs- GmbH
Official OpenERP Partner
References