Model methods for client interaction
We have seen the most important model methods used to generate recordsets and how to write on them. But there are a few more model methods available for more specific actions, as shown here:
read([fields])
: This is similar to browse, but instead of a recordset, it returns a list of rows of data with the fields given as it's argument. Each row is a dictionary. It provides a serialized representation of the data that can be sent through RPC protocols and is intended to be used by client programs and not in server logic.search_read([domain], [fields], offset=0, limit=None, order=None)
: This performs a search operation followed by a read on the resulting record list. It is intended to be used by RPC clients and saves them the extra round trip needed when doing a search first and then a read.load([fields], [data])
: This is used to import data acquired from a CSV file. The first argument is the list of fields to import, and it maps directly to a CSV top row...