I agree to Idea Drop OIDS (PostgreSQL)
Voting Disabled

4 votes

I disagree to Idea Drop OIDS (PostgreSQL)

Rank5

Idea#32

This idea is active.
PostgreSQL »

Drop OIDS (PostgreSQL)

) drop the addition of "with (oids=false)" completely in the generated SQL (if it's unchecked). It only clutters the generated SQL and nowadays does not server any purpose as it's the default anyway (as oids are deprecated).

Submitted by Vaclav 2 years ago

Vote Activity Show

Events

  1. The idea was posted
    2 years ago

Comments (3)

  1. I agree, but default setting for this feature should be considered. It is true that config variable "default_with_oids = off" is set by default, but what about systems with this variable set to "on" ?

    Maybe there are no any, but who knows. I would add behaviour switch in model config.

    2 years ago
    0 Agreed
    0 Disagreed
  2. I agree with MichalK that it needs to be a setting. I think the best way is default to no oids, except if you have specifically requested it for a table.

    The reason you want to be able to add them to a table is because programs like MS Access, being used as a front end into a Postgres database, get confused when updating tables without oids. Once you update the table, you can do longer view any records until you close and re-start access. If you turn on oids for tables that you are editing within MS Access, then you don't have any problems.

    1 year ago
    0 Agreed
    0 Disagreed
  3. (Off topic) So how does MS Access work with databases that do not have OIDs at all? It should be able to use regular primary keys, shouldn't it?

    1 year ago
    0 Agreed
    0 Disagreed