- Provides a new attachment location to save attachment as large
- objects. To enable the large object storage option change the
- ir_attachment.location
- parameter to
- lobject
- .
-
Technical module to extend the Base Automation - module. Another trigger is added, which executes the action during - creation, update and deletion. The new trigger can now be selected - in the From View of Base Automation.
-Allows the administrator to create rules to - automatically garbage collect a certain model. Every rule can have a - different time interval additional constraints. An extra constraint - can be for example to only delete inactive records.
-Technical module to provide some utility - features. The module is mainly used as a dependency by other modules - and to provide a collection of common libraries. This module has no - direct visible effect on the system. It provides functions to - convert data from one file format to another.
-Provides a field to store bytes as PostgreSQL large objects. - PostgreSQL offers support for large objects, which provide - stream-style access to user data that is stored in a special - large-object structure. They are useful with data values too large - to be manipulated conveniently as a whole.
-
- Psycopg allows access to the large object using the
- lobject
- class. Objects are generated using the
- connection.lobject()
- factory method. Data can be retrieved either as bytes or as Unicode
- strings.
-
- Psycopg large object support efficient import/export with file
- system files using the
- lo_import()
- and
- lo_export()
- libpq functions.
-
Changed in version 2.6: added support for large objects - greated than 2GB. Note that the support is enabled only if all the - following conditions are verified:
-
- If Psycopg was built with 64 bits large objects support (i.e. the
- first two contidions above are verified), the
- psycopg2.__version__
- constant will contain the lo64 flag. If any of the contition is not
- met several lobject methods will fail if the arguments exceed 2GB.
-
-
-from odoo.addons.muk_fields_lobject.fields.lobject import LargeObject
-
-class LargeObjectModel(models.Model):
-
- data_content = LargeObject(string="Data")
-
- @api.multi
- def data(self):
- for record in self:
- bytes = record.data_content
- oid = record.with_context({'oid': True}).data_content
- size = record.with_context({'bin_size': True}).data_content
- stream = record.with_context({'stream': True}).data_content
-
-
-
- Allow records to be grouped by hour. Similar to the already
- existing options (
- day, week, month, quarter, year
- ). Just add the paramerter
- groupby='date:hour'
- like shown below.
-
-
-@api.multi
-def sales_per_hour(self):
- daily_sales = self.env['sale.report'].read_group(
- domain=[],
- fields=['date', 'price_subtotal'],
- groupby='date:hour')
- return daily_sales
-
-
- Technical module to provide some utility and - security features. The module is mainly used as a dependency by - other modules and has no direct visible effect on the system.
-Technical module to provide some utility - features and libraries that can be used in other applications. This - module has no direct effect on the running system. It has no direct - visible effect on the system.
-Technical module to provide some utility - features. The module is mainly used as a dependency by other modules - and to provide a collection of common libraries. It has no direct - visible effect on the system.
-