openerp-india team mailing list archive

["Jignesh Rathod\(OpenERP\)" <984976@xxxxxxxxxxxxxxxxxx>]

Hello Patrick ,

Thanks for your contribution.

I have applied your patch and it's solved the problem.

This issue has been fixed following branch and rev no , rev id.

lp:~openerp-dev/openobject-server/trunk-bug-984976-jir

rev no : 4150
rev id :   4150 jir@jir-desktop-20120427112622-wacq0vhq8mzjrgbb

Thanks.




** Changed in: openobject-server
       Status: Confirmed => Fix Committed

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

Title:
  ids of type long fails in users.read() (res_users.py)

Status in OpenERP Server:
  Fix Committed

Bug description:
  If an ids of type long is passed to method users.read(), the returned result is erroneous.
  The problem occurs because long ids should be treated the same way as ints, but are not.

  discovered in community version 6.1-1 running on Linux 64bits.

  You can reproduce the error using the ldap addon (i did it with the web client) (and yes, I know users_ldap.py should be fixed too!):
  1) configure the LDAP addon according to one of your ldap servers. Check the "create user" flag.
  2) login to openerp with an ldap user that is not yet configured in openerp.
  3) Click the "human resources" icon --> server error.
  4) if you logout then login again, the error does not occur: the users_ldap addon sets an integer user_id when the user already exists, a long user_id if it has just been created.

  The attached patch fixes this problem. But the proper test should
  probably be fully in phase with the test at the end of Models.read()
  (orm.py).

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