openerp-india team mailing list archive

["Stefan Rijnhart \(Therp\)" <1237310@xxxxxxxxxxxxxxxxxx>]

Hi Mohammed,

I'm removing OCB-addons as an affected project for this bug as per
project policy. Of course the bug affects ocb-addons/7.0 by definition
as well as openobject-addons but we only want to track bugs that we fix
in OCB-specific changes. Therefore, you should only add bugs to the
project that you are going to propose a solution for.

Thanks,
Stefan.


** No longer affects: ocb-addons/7.0

** No longer affects: ocb-addons

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1237310

Title:
  [account][7.0][trunk] Bank/cash statements action views have the same
  sequence value '1'

Status in OpenERP Addons (modules):
  Confirmed

Bug description:
  In the file 'account/account_view.xml' the action views
  (ir.actions.act_window.view) for the model account.bank.statement uses
  the same sequence. This may randomize the order of bank/cash statement
  views (ex. show form view by default instead of list view)

  By default, the views are shown in the correct order because they are
  inserted in that order when the module was first installed. But,
  later, when PostgreSQL autovacum kicks-in, it may change the physical
  order of data. The default order of data returned by postgresql is
  undefined.

  I found this bug when the cash register menu started to show graph
  view by default instead of the list view.

  To check if other views have the same problem, I used the following
  query:

  select (select module||'.'|| name from ir_model_data where model='ir.actions.act_window' and res_id=act_window_id) model,
              sequence, count(*)
  from ir_act_window_view
  group by act_window_id, sequence
  having count(*)>1
  order by act_window_id, sequence;

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1237310/+subscriptions