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". With this information, the client is able to solve the problem by himself. I'd like to have your opinion and suggestion before i start to code some possibile workarounds best regards, -- Davide Corio email: davide.corio<at>domsense.com web: http://www.domsense.com _______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
