Datagrip is displaying question marks within the DDL for my tables that have foreign keys, what is this and how can I fix it?

Hello, thank you for the reply. I updated my IDE to 2024.3.4, and the problem still persists.

Here is one such example: 

-- auto-generated definition
create table center
(
    id              serial
        primary key,
    external_id     varchar(255),
    external_source varchar(255),
    name  text
)
    using ???;

alter table center
    owner to table_owner;

create unique index center_external_id_external_source
    on center using ??? (external_id, external_source);

create unique index center_external_id_external_source_site_text
    on center using ??? (external_id, external_source, name);

grant select on center to read_only_user;

 

Thanks for the update. 

The access method is absent in your screenshot. I tested create table DDL statement using various default access methods in postgres and in my case, it's showing the using portion correctly. It seems like we couldn't retrieve the meta of this object. Do you know if it's a custom access method used in this table and are you able to locate it in the Database Explorer under Database Objects?
 

Hey, I hope this information helps:

So,  when I go to that location I see 

when I run SELECT * from pg_am, which should give information about what is supported (or so I read) I see this:

So the containers with objects are not listed under Database Objects, which could be causing this issue. Please check if you have pg_catalog schema enabled for introspection. You may want to additionally refresh the database you're working with. See if the access methods are shown afterward
 

Hey,  I'm not sure what you mean by “Please check if you have pg_catalog schema enabled for introspection. ”, but I did the following:

• invalidated cache and restarted,
• refreshed the database,
• made sure pg_catalog was under schemas,
• checked “all schemas” as you've shown in your image,
• verified that “pre-inspected objects are used” is next to pg_catalog, like in your image,
• went to properties→schema→and checked pg_catalog there

The problem still persists, and I've noticed the issue on other databases within Datagrip since first making this post, for unrelated projects that I have. So I'm thinking it's something to do with Datagrip itself. They do not have the problem when inspecting the DDL by connecting to it outside of Datagrip, from a third party.

Any other ideas?