Closed (outdated)
Project:
Event
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Jun 2009 at 00:19 UTC
Updated:
13 Apr 2018 at 21:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
killes@www.drop.org commenteddoes pgsql take exception on the negative value for the int?
Comment #2
killes@www.drop.org commentedComment #3
protools commentedPostgres 8.4
User-configurable time zones:
+ Enabled
When enabled, users can set their own time zone
and
* warning: pg_query() [function.pg-query]: Query failed: ERROR: value too long for type character varying(8) in D:\BitNami WAPPStack\apache2\htdocs\blogmybaby\includes\database.pgsql.inc on line 139.
* user warning: query: UPDATE users SET timezone = '322|14400', name = 'luk911', mail = 'luk911@mail.ru', status = '1', data = 'a:7:{s:17:"messaging_default";s:4:"mail";s:27:"notifications_send_interval";s:1:"0";s:18:"notifications_auto";i:0;s:14:"picture_delete";i:0;s:14:"picture_upload";s:0:"";s:7:"contact";i:0;s:13:"form_build_id";s:37:"form-21643c66a27321b15e39b51d90609bf0";}' WHERE uid = 1 in D:\BitNami WAPPStack\apache2\htdocs\blogmybaby\modules\user\user.module on line 247.
Comment #4
rbroberts commentedThe issue is the timezone is declared as varchar(8) and the query is supplying an integer. There is no automatic type conversion, so the query should be
Note the quotes around the timezone value.
Comment #5
rbroberts commentedI'm not sure if I should create a separate item against 5.x-2.x-dev, but the problem is present there, which is what my previous post was testing. I'm attaching a patch for 5.x-2.x-dev, but it may apply to 6.x also.
Comment #6
rbroberts commentedHere is a patch against 6.x
Comment #7
rbroberts commentedChanging status to hopefully trigger some action.
Comment #8
moskito commentedI am also using Postgres 8.4 with D6 and patch in #6 worked perfectly.
Comment #9
moskito commentedAlmost 5 weeks without bad reviews, I guess it can be set as reviewed.
Comment #10
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.