Re: Upgrade error

["G. Net" <..hidden..>]

OK it works now...

GRANT SELECT ON TABLE custom_table_catalog TO mylsmbuser;
GRANT SELECT ON TABLE custom_field_catalog TO mylsmbuser;

thanks for input

One small immediate niggle - there's a glitch in the nav menu (css?) whereby the mouseover causes the links to jump up and down which is distracting. its worse when there are several levels expanded.

you mentioned sql to sort out the dups ?

----- Original Message ----
From: Chris Travers <..hidden..>
To: ..hidden..
Sent: Sunday, 12 November, 2006 1:51:06 AM
Subject: Re: [Ledger-smb-users] Upgrade error

Not sure what causes that session issue.  Chris M?  At any rate you
should be able to get rid of it by closing all web browser windows and
starting again.

The other issue (permission denied) happens when the table is created
by Postgres (or another user) and not by the one you are loggin in as.

This table holds information about custom fields which have been added
to existing objects.  You can probably safely give select privilege to
everyone.  However, it is not safe to give other priveleleges if you
are concerned about security.

GRANT SELECT ON TABLE custom_table_catalog TO PUBLIC;
GRANT SELECT ON TABLE custom_field_catalog TO PUBLIC;

Best Wishes,
Chris Travers.

On 11/11/06, G. Net <..hidden..> wrote:
> > Here is what we can do to make this minimally operational:
> >
> > go into the sql/Pg-upgrade-2.6.18-2.6.19.sql file and copy everything
> > below the rules which add the items into transactions (i.e. the
> > custom_table_catalog definition and the like).
> >
> > Basically run every command other than those create rules and insert
> > commands.  Then make sure that the line in Form.pm whcih sets
> > {dbversion} i set to 2.6.19.