Error on PostgreSQL 9.3 REVERSE ENGINEERING tables

[pellicano]

"Table xxxxx_xxxxx has no primary key. Doctrine does not support reverse engineering from tables that don't have a primary key."

This table was on PUBLIC schema and with a PK composed by 3 fields.

[doctrinebot]

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DBAL-733

We use Jira to track the state of pull requests and the versions they got
included in.

[beberlei]

This Pull-Request breaks the PostgreSQL tests, see https://travis-ci.org/doctrine/dbal/jobs/16026906

[pellicano]

The test was executed on PostgreSQL version 9.3?

Att,
Marcelo Pellicano de Oliveira.

2013/12/29 Benjamin Eberlei notifications@github.com

This Pull-Request breaks the PostgreSQL tests, see
https://travis-ci.org/doctrine/dbal/jobs/16026906

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/466#issuecomment-31320149
.

[deeky666]

No I think Travis uses 9.1 as default. Can you please explain a bit more what your patch does and why it is necessary? Looks rather weird why this should work on 9.3 but not below.

[pellicano]

I have a table with 3 fields composing a primary key and when I tried to do
the reverse engineering, I got the message that the my table didn't have
any PK.
I debugged the core and I realised that this part of the query was not
retrieving the fields PK as they are:
select string_to_array((select replace(setting,'"$user"',user) from
pg_catalog.pg_settings where name = 'search_path'),',')

the result was:
"{""$user""," public"," topology"}"

and when I changed to:
select string_to_array((select replace(setting,'"$user"',user) from
pg_catalog.pg_settings where name = 'search_path'),', ')

the result was:
"{""$user"",public,topology}"

In other words, the "public" schema was to maching the realname the table
name.
If you need more explanations, just let me know.

Att,
Marcelo Pellicano de Oliveira.

2013/12/29 Steve Müller notifications@github.com

No I think Travis uses 9.1 as default. Can you please explain a bit more
what your patch does and why it is necessary? Looks rather weird why this
should work on 9.3 but not below.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/466#issuecomment-31329229
.

[deeky666]

@pellicano Can you please confirm whether this is a duplicate of PR #492?

[pellicano]

Yup, Steve.

Em sábado, 4 de janeiro de 2014, Steve Müller escreveu:

@pellicano https://github.com/pellicano Can you please confirm whether
this is a duplicate of PR #492 #492?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/466#issuecomment-31594169
.

Att,
Marcelo Pellicano de Oliveira.

[deeky666]

Closing this in favour of PR #492