Updated Postgres dbase scripts

We just successfully got Track+ 3.2 to work with Postgresql 8.0 on Solaris 9. There were some tweeks to the scripts

1) In dbase\postgres\track-schema.sql, all refernces to the 'group' column should be 'thegroup'

2) Indbase\postgres\permissions.sql, the script needed the following additions:

GRANT ALL PRIVILEGES ON TATTRIBUTE TO friedj;
GRANT ALL PRIVILEGES ON TREPORTLAYOUT TO friedj;
GRANT ALL PRIVILEGES ON TWORKFLOW TO friedj;
GRANT ALL PRIVILEGES ON TPLISTTYPE TO friedj;
GRANT ALL PRIVILEGES ON TSITE TO friedj;
GRANT ALL PRIVILEGES ON TPROJECTTYPE TO friedj;

Just wanted to share our findings for those trying to use postgresql.

Thanks!

Great, thanks! We will include this in the development trunk.

rockman wrote:We just successfully got Track+ 3.2 to work with Postgresql 8.0 on Solaris 9. There were some tweeks to the scripts

1) In dbase\postgres\track-schema.sql, all refernces to the 'group' column should be 'thegroup'

2) Indbase\postgres\permissions.sql, the script needed the following additions:

GRANT ALL PRIVILEGES ON TATTRIBUTE TO friedj;
GRANT ALL PRIVILEGES ON TREPORTLAYOUT TO friedj;
GRANT ALL PRIVILEGES ON TWORKFLOW TO friedj;
GRANT ALL PRIVILEGES ON TPLISTTYPE TO friedj;
GRANT ALL PRIVILEGES ON TSITE TO friedj;
GRANT ALL PRIVILEGES ON TPROJECTTYPE TO friedj;

Just wanted to share our findings for those trying to use postgresql.

Thanks!

With regard to step #2, has something changed? I see no mention of a "friedj" user in the installation docs. The only user mentioned is "trackp", the owner of the database.

Have you noticed long authentication delays with the Postgresql integration?

See:
http://www.trackplus.com/forum/posts/list/36.page

With regard to step #2, has something changed? I see no mention of a "friedj" user in the installation docs. The only user mentioned is "trackp", the owner of the database.

No, not really. Since 3.2 the user manual has changed the database user from friedj to trackp. However, the privileges script still had friedj in there.

The name really doesn't matter, as long as it is the same here, in the Torque.properties file, and the database system.