c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Friday 08 April 2011, you wrote:
> 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


This has been fixed in openerp looooong ago..
Please update your installation.

-- 
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)