[Tickets #7490] Re: upgrade from 1.0.1 to 1.1.3 fails with pgsql error

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7490
------------------------------------------------------------------------------
  Ticket             | 7490
  Updated By         | chris at vandenberghe.org
  Summary            | upgrade from 1.0.1 to 1.1.3 fails with pgsql error
  Queue              | Horde Groupware
  Version            | 1.1.3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


chris at vandenberghe.org (2008-10-20 00:28) wrote:

Hi,

I have the following tables (in schema.table format) in database bobo:

public.users
postfix.domains
postfix.forwardings
horde.* (all the horde tables)

The horde db user is the owner of the horde schema (and has it a first  
schema in the search path), has select rights on public.users and no  
rights on any other schema/table.

public.forwardings contains the forwarding table for postfix (local  
email -> external email) and should not be accessed by anything else  
than postfix.  I have grep'ed in the horde directory for 'forwardings'  
but could not find this string back.

Using postgres schema's _should_ not be an issue, as new tables under  
the horde user are created in the horde schema automatically (if not  
specified differently) and select/alter on a table should find the  
correct schema automatically (again if not specified differently).

Hope this helps...

Regards,
Chris.