damien
/
muk_base
mirror of https://github.com/muk-it/muk_base
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53 Commits
5 Branches
0 Tags
14 MiB
Tree: 2791cb1570
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2791cb1570'
${ noResults }
muk_base/muk_fields_lobject
Mathias Markl 2791cb1570
Update test_attachment.py 		7 years ago
..
controllers Update main.py 7 years ago
doc u 7 years ago
i18n u 7 years ago
static/description u 7 years ago
LICENSE test 7 years ago
README.md update 7 years ago
__init__.py controller 7 years ago
__manifest__.py Update __manifest__.py 7 years ago
fields.py test 7 years ago
models.py init 7 years ago

README.md

MuK Large Objects Field

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:

  • the Python build is 64 bits;
  • the extension was built against at least libpq 9.3;
  • the server version is at least PostgreSQL 9.3 (server_version must be >= 90300).

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.