postgresql initialization not working properly with DB-Prefix

[rcubetrac]

Reported by imlich on 28 Apr 2014 11:05 UTC as Trac ticket #1489839

in the past I have separated data from different roundcube versions by using different schemas in postgresql and tweaking the code such that the search_path is set accordingly.

Now upgrading to 1.0.0 I thought to give the installer a try and using a DB-Prefix instead of separate schema.

fix_table_names in rcmail_installer.php is not working properly:

A) INDEXES are not handled. So adding a similar code as for CREATE SEQUENCE will help.

B) CONSTRAINTS/INDEXES are not handled properly if they have an explicit name, as the DB-Prefix would need to be added, e.g. in table "users", it should read:
CONSTRAINT DBPREFIXusers_username_key UNIQUE (username, mail_host) as you get otherwise naming conflicts. The easiest to avoid this is NOT to use explicit names for constraints and indexes. Postgresql will then create unique names (which will be according to {tablename}{columnname(s)}{suffix} ).

Keywords: postgresql,initialization,schema,prefix
Migrated-From: http://trac.roundcube.net/ticket/1489839

[rcubetrac]

Comment by @alecpl on 29 Apr 2014 09:59 UTC

Fixed in 90f7aa9

[rcubetrac]

Status changed by @alecpl on 29 Apr 2014 09:59 UTC

new => closed