Abdoul Cissé

The inheritance feature for Postgres is just for modeling purposes since it's actually not using a common table for sharing those common columns. It will append that list of columns...

So perhaps the issue is just about skipping the base declaration table from on entity generation and that's all. Everything else is fine.

@jeanfortheweb Have you taken a look at this by any chance?

@jeanfortheweb, I'm using the latest version of the fixture library. Let's discard that. While trying to reproduce the issue in a minimalistic project I found, that the root cause was...

From what I can recall, TypeORM always looks for entity field names in that array in the Index declaration, so either you could be pointing to an entity field directly...

Hi @jeanfortheweb. Any luck digging into this scenario?

@jeanfortheweb. Another scenario I found uses a regular primary key. The problem was reduced to the fact that something really strange happens when having fixtures for entities declaring primary keys...

Hi @jeanfortheweb I spent some time today extending the complex bundle coming in tests with an additional entity called project. This new entity has got fields that are foreign key...

Here's the fork that I used to extend one of the test scenarios https://github.com/acisser/typeorm-fixture-builder

@jeanfortheweb Submitted PR #67 with the fix. Please let me know any comments.