c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #21492
[Bug 754582] [NEW] indexing ir_translations fails for long tranlatable strings
Public bug reported:
take the example of a long-long product description, and translate it to
a different language, I've ended up with the following error:
index row size 3120 exceeds maximum 2712 for index "ir_translation_ltns"
HINT: Values larger than 1/3 of a buffer page cannot be indexed.
Consider a function index of an MD5 hash of the value, or use full text
indexing.
the solution is here
http://archives.postgresql.org/pgsql-general/2011-03/msg00430.php
according to the discussion that follows, it seems to be wise to use md5 (os similar) indexing by default. If this is the case, how would one implement it?
(Actually, a simple ALTER TABLE did it for the existing database)
** Affects: openobject-server
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/754582
Title:
indexing ir_translations fails for long tranlatable strings
Status in OpenERP Server:
New
Bug description:
take the example of a long-long product description, and translate it
to a different language, I've ended up with the following error:
index row size 3120 exceeds maximum 2712 for index "ir_translation_ltns"
HINT: Values larger than 1/3 of a buffer page cannot be indexed.
Consider a function index of an MD5 hash of the value, or use full text
indexing.
the solution is here
http://archives.postgresql.org/pgsql-general/2011-03/msg00430.php
according to the discussion that follows, it seems to be wise to use md5 (os similar) indexing by default. If this is the case, how would one implement it?
(Actually, a simple ALTER TABLE did it for the existing database)
Follow ups
References