Closed (duplicate)
Project:
Views (for Drupal 7)
Version:
6.x-2.3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
8 Feb 2009 at 07:11 UTC
Updated:
12 Mar 2009 at 04:06 UTC
FYI, I get this one with PostgreSQL when updating from 2.2 to 2.3
I have no clue how you can change a bytea into a text so here we are. Although this is not too serious since only the cache is affected... What I would suggest is that you just drop the cache (DELETE FROM views_object_cache) then ALTER the type of the data column and be done with it.
Thank you.
Alexis Wilke
Comments
Comment #1
tuxave commentedThis threw me for a loop as well. At first I thought that the column was supposed to be bytea after the module update, but a quick view of the code suggest the new type is text. I confirmed my back shows the column to be bytea.
I suspect this is either a bug in the database.pgsql.inc file or the views module makes a wrong assumption about casting data under these circumstances.
Comment #2
sammys commentedThanks for posting the issue. I can't replicate the bug with D6 6.9 and PostgreSQL 8.3. What version are your D6/PostgreSQL at?
We might need to move this to be a core issue (my realm).
Comment #3
AlexisWilke commentedsammys,
I have 6.9 too.
However, my two servers have PostgreSQL 8.2.
psql (PostgreSQL) 8.2.7
psql (PostgreSQL) 8.2.9
So I guess that is an issue in older versions only.
Thank you.
Alexis Wilke
Comment #4
merlinofchaos commentedThe problem is line 223 of includes/cache.inc:
should be
Can someone with pgsql verify that this fixes the problem?
Comment #5
josh waihi commentedthis has been fixed here #373225: views database update warnings on postgresql. Its a core issue that need to be commited
Comment #6
sammys commentedThis bug is a duplicate of the one in http://drupal.org/node/373225 so i'm marking this as a duplicate. We shall continue this sucker in that issue.