env(Environment) in new API is to provide an encapsulation around cursor, user_id, model, and context, Recordset and caches.
It evades the use of infamous function signature def afun(self, cr, uid, ids, context=None): and in new API its def afun(self):
And if you want to call ORM method directly from an object you can use self.env['obj'].method instead of self.method
For more about env:- Link
Hope this helps.
self.env['model.name'] is used instead of self.pool.get('model.name') in the old api, to access the recordset of a particular model. In the old api, with search and browse you had pass cr, uid, context seperately, whereas with self.env it is implicit.
An environment wraps data for ORM records:
'cr', the current database cursor.
'uid', the current user id.
'context', the current context dictionary.
You may check this link:
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 10/16/15, 12:09 AM|
|Seen: 4737 times|
|Last updated: 12/1/15, 4:43 AM|