Home » Authentication » LiveUser » Bug #4593

[2005-06-14 20:13 UTC] soox at gmx dot net

Description:
------------
during installation of the db-schema (with sql/
install.php) i get the follow error:
Last query: CREATE UNIQUE INDEX id_i ON
liveuser_right_implied (right_id, implied_right_id)]
[Native message: ERROR: relation "id_i" already exists

i get the same troubles with the index "define_name_i"

postgress can't have two equal index names even in
diffrent tables.

Actual result:
--------------
output of sql/install.php:

....
int(1)
bool(true)
Debug messages
beginTransaction(4): starting transaction
query(4): BEGIN
*a_lot_of_sql_stuff*
query(4): CREATE UNIQUE INDEX id_i ON
liveuser_userrights (perm_user_id, right_id)
*a_lot_of_sql_stuff*
query(4): CREATE UNIQUE INDEX id_i ON
liveuser_right_implied (right_id, implied_right_id)
rollback(4): rolling back transaction
query(4): ROLLBACK

object(MDB2_Error)#17 (8) {
["error_message_prefix"]=>
string(0) ""
["mode"]=>
int(1)
["level"]=>
int(1024)
["code"]=>
int(-5)
["message"]=>
string(26) "MDB2 Error: already exists"
["userinfo"]=>
string(151) "[Last query: CREATE UNIQUE INDEX id_i ON
liveuser_right_implied (right_id, implied_right_id)]
[Native message: ERROR: relation "id_i" already exists]
"
....

[2005-06-15 09:25 UTC] smith at backendmedia dot com

so I guess all that needs to happen is prefix all indexes with the table name?

[2005-06-15 11:10 UTC] smith at backendmedia dot com

This bug has been fixed in CVS.

In case this was a documentation problem, the fix will show up at the
end of next Sunday (CET) on pear.php.net.

In case this was a pear.php.net website problem, the change will show
up on the website in short time.

Thank you for the report, and for helping us make PEAR better.