PRIMARY KEY only for table, FOREIGN TABLE not support it

[ermolaev]

No description provided.

[ermolaev]

hello @lfittl, why you not accept my pull request?

[lfittl]

@ermolaev Sorry, been very busy. Thanks for your contribution!

It seems that this wouldn't work if the id column was not listed first in the table - is there a way we can implement this where it allows other columns to be listed in between?

[ermolaev]

Yes you are right!
I fixed it.

[lfittl]

@ermolaev Sorry for not getting back about this - could you re-base this PR?

[olleolleolle]

@ermolaev Your changes look good, could you rebase on top of current master?

[andyatkinson]

@ermolaev @olleolleolle Hello. It's been a long time, but I'm wondering if there's still interest in getting this functionality into the gem?

If so, please confirm that, and please rebase the changes on the latest version of the master branch.

If you could expand on the use case a bit, and ideally include some sample schema that shows a positive and negative example, possibly as documentation, that would help understand the purpose and how to verify this functionality while avoiding a regression.

If there's no response here after a month, then we'll likely close this out. Thanks.

[ermolaev]

I think this PR may be closed, now I support fork https://github.com/corp-gp/activerecord-clean-db-structure

this fork fixed some problems with running migration (via web interface) and added conditions for working with timescaledb, fdw, fillfactor option