Postgresql Installation Failure
mrlovecraft - June 12, 2008 - 10:06
| Project: | Drupal |
| Version: | 5.x-dev |
| Component: | language system |
| Category: | bug report |
| Priority: | normal |
| Assigned: | NancyDru |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
When trying to install this module on Drupal 5.7 using Postgresql 8.2.6, this error is displayed:
* warning: pg_query() [function.pg-query]: Query failed: ERROR: value too long for type character varying(255) in F:\webs\drupal57\includes\database.pgsql.inc on line 125.
* user warning: query: UPDATE locales_source SET location = ' Copy of taxonomy_image.module:346 taxonomy_image.module:339 taxonomy_image.info:0;0 contributed/taxonomy_image_blocks/taxonomy_image_blocks.info:0 contributed/taxonomy_image_link_alter/taxonomy_image_link_alter.info:0 contributed/taxonomy_image_node_display/taxonomy_image_node_display.info:0' WHERE source = 'Taxonomy Image' in F:\webs\drupal57\includes\database.pgsql.inc on line 144.
#1
It seems that there is a problem with a line at 'es.po' file (spanish translation):
#: Copy of taxonomy_image.module:346 taxonomy_image.module:339 taxonomy_image.info:0;0 contributed/taxonomy_image_blocks/taxonomy_image_blocks.info:0 contributed/taxonomy_image_link_alter/taxonomy_image_link_alter.info:0 contributed/taxonomy_image_node_display/taxonomy_image_node_display.info:0
This previous line is too long, 296 chars, and pg_query only seems to handle 255 chars.
Any clue on how can I solve it?
Thanks in advance
#2
Two problems detected:
- many typos in file 'es.po' => that seems to me, but I would really appreciate an expert opinion
- problem when trying to install the module using Postgresql. The sentece for the creation of term_image table seems to be wrong.
#3
Well, I don't speak Spanish, so I wouldn't be a good judge. But I think I'll see if I can get the Potx owner to look at this issue too.
Do you know what the correct installation code would be? I don't have Postgres either. I'll be happy to fix it if we can figure it out.
#4
I changed the CREATE, taking out "CHECK (VALUE>=0)". It will be in the next -dev roll up.
BTW, feel free to make an updated Spanish translation.
#5
#6
This is a Drupal core bug. Drupal core should trim the string if it exceeds the allowed location length, when importing / updating. Please test with latest Drupal 5 core and try to reproduce.