Is this still causing you problems?
broadbandvoice wrote:
I noticed we still using a2billing-pgsql-schema-v1.3.0.sql; could this be the problem.
To install the schema for a fresh v1.3.1 you first need to pass that v1.3.0 schema to your DB server, then also pass it the
UPDATE-a2billing-v1.3.0-to-v1.3.1-pgsql.sql update script.
Quote:
a2billing=> SELECT * FROM cc_ui_authen;
ERROR: relation "cc_ui_authen" does not exist
You need to install the schemae using the a2billing user too, otherwise they won't be visible to it.
Quote:
Querying SQL Server System Tables is what is giving me problems. I beleive the postgres is installed and running but not able to query the system tables.
a2billing=> SELECT * FROM cc_ui_authen;
ERROR: relation "cc_ui_authen" does not exist
That's not what that error message is saying I think. It's simply complaining that the A2B table cc_ui_authen hasn't yet been created by the current Postgres user.
The whole procedure should look like (you may need to substitute 'postgres' with you Postgres super user account name, often 'root'):
Code:
$ createuser -d -P -E -U postgres -W a2billing
Enter password for new role: $a2bpass
Enter it again: $a2bpass
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create more new roles? (y/n) n
Password: $postgrespass
CREATE ROLE
$ createdb -U a2billing -W a2billingdb
Password: $a2bpass
CREATE DATABASE
$ psql -d a2billingdb -U a2billing -W -f DataBase/psql/a2billing-pgsql-schema-v1.3.0.sql
Password for user a2billing: $a2bpass
$ psql -d a2billingdb -U a2billing -W -f asterisk2billing/branches/1.3/DataBase/psql/UPDATE-a2billing-v1.3.0-to-v1.3.1-pgsql.sql
Password for user a2billing: $a2bpass
$ psql -d a2billingdb -U a2billing -W -c 'SELECT * from cc_ui_authen;'
Password for user a2billing: $a2bpass
userid | login | password | groupid | perms | confaddcust | name | direction | zipcode | state | phone | fax | datecreation
--------+-------+------------+---------+-------+-------------+------+-----------+---------+-------+-------+-----+----------------------------
2 | admin | mypassword | 0 | 32767 | | | | | | | | 2005-02-26 21:14:05.391501
1 | root | myroot | 0 | 32767 | | | | | | | | 2005-02-26 20:33:27.691314
(2 rows)
You'll get some warnings about duplicate keys from the v1.3.1 upgrade. These are the footprints of a tired Stavros hacking on the schema some time ago and not thinking clearly.
They are harmless though, I promise.
Login
Register
FAQ
Search
