[horde] Turba errors after updating to 2.2

Michael Rubinsky mrubinsk at horde.org
Sat Mar 1 16:52:11 UTC 2008


Quoting Johan Huldtgren <johan+horde at obitus.org>:

> When I try to browse my address book (sql based), I get:
>
> DB Error: no such field.
>
> This is after I've run 2.1_to_2.2_sql_schema.php  (which went
> through without errors).
>
>  From my PostgreSQL log, I see this:
>
> Mar  1 16:53:11 www postgres[67939]: [20-1] LOG:  statement: SELECT
> object_id, object_type, owner_id, object_name, object_email,
> object_company FROM turba_objects WHERE  (owner_id = 'johan')
> Mar  1 16:53:11 www postgres[67939]: [21-1] ERROR:  column
> "object_name" does not exist at character 42
>
> So it seems that somewhere turba is still referencing object_name

You probably didn't update your configuration files to reflect the new  
schema that you decided to use when you ran the update script.  
Specifically, servers.php

> which gets dropped in the schema update. Taking a look at the
> schema for turba_objects, we see that there is no object_name anymore.

<snip>

> So how does one solve this?

 From doc/UPGRADING:

" Don't forget to update your configuration files or to re-create them  
from the ``.php.dist`` examples."


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org

"Time just hates me. That's why it made me an adult." - Josh Joplin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: PGP Digital Signature
Url : http://lists.horde.org/archives/horde/attachments/20080301/e4b4a93d/attachment.bin 


More information about the horde mailing list