Bug #119911 for SQL-Translator: S::T::Producer::PostgreSQL produce UNIQUE CONSTRAINT instead of UNIQUE INDEX

Thu Jan 19 09:35:35 2017 KES [...] cpan.org - Ticket created

Subject:

S::T::Producer::PostgreSQL produce UNIQUE CONSTRAINT instead of UNIQUE INDEX

https://metacpan.org/source/ILMARI/SQL-Translator-0.11021/lib/SQL/Translator/Producer/PostgreSQL.pm#L551

Fri Feb 24 09:58:58 2017 wolfsage [...] gmail.com - Correspondence added

From:

wolfsage [...] gmail.com

On Thu Jan 19 09:35:35 2017, KES wrote: Show quoted text

> https://metacpan.org/source/ILMARI/SQL-Translator- > 0.11021/lib/SQL/Translator/Producer/PostgreSQL.pm#L551

I think the complaint here is that if you say: $sqlt_table->add_index( name => 'new_index', fields => [ 'lower(some_column)' ], type => 'unique', ); the producer tries to create it as a CONSTRAINT in the table definition (which is invalid) rather than a 'CREATE INDEX' statement which would allow things like 'lower(some_column)'. This makes add_index not-very-useful for a lot of cases.

Fri Feb 24 09:58:59 2017 The RT System itself - Status changed from 'new' to 'open'

Fri Feb 24 11:47:16 2017 KES [...] cpan.org - Correspondence added

I have introduce next changes to workaround the problem. https://github.com/dbsrgits/sql-translator/issues/82#issuecomment-276290608 I do not know how to fix that correctly. Hope it will help.