referential_key_table_name empty for multi-column index (Option::unwrap on None during migration)

[avdb13]

Hi, getting an error when using the CLI to generate a schema query. Spent a while trying to figure out what's wrong but I'm clueless. Below is the definition of the table and index that are causing issues. Let me know if you need more.

                                          Table "public.current_state_events"
        Column         |  Type  | Collation | Nullable | Default | Storage  | Compression | Stats target | Description
-----------------------+--------+-----------+----------+---------+----------+-------------+--------------+-------------
 event_id              | text   |           | not null |         | extended |             |              |
 room_id               | text   |           | not null |         | extended |             |              |
 type                  | text   |           | not null |         | extended |             |              |
 state_key             | text   |           | not null |         | extended |             |              |
 membership            | text   |           |          |         | extended |             |              |
 event_stream_ordering | bigint |           |          |         | plain    |             |              |
Indexes:
    "current_state_events_event_id_key" UNIQUE CONSTRAINT, btree (event_id)
    "current_state_events_member_index" btree (state_key) WHERE type = 'm.room.member'::text
    "current_state_events_room_id_type_state_key_key" UNIQUE CONSTRAINT, btree (room_id, type, state_key)
    "current_state_events_stream_ordering_idx" btree (event_stream_ordering)
Foreign-key constraints:
    "event_stream_ordering_fkey" FOREIGN KEY (event_stream_ordering) REFERENCES events(stream_ordering) NOT VALID
    

 Index "public.current_state_events_room_id_type_state_key_key"
  Column   | Type | Key? | Definition | Storage  | Stats target
-----------+------+------+------------+----------+--------------
 room_id   | text | yes  | room_id    | extended |
 type      | text | yes  | type       | extended |
 state_key | text | yes  | state_key  | extended |
unique, btree, for table "public.current_state_events"

[2024-01-29T12:48:56Z DEBUG sea_schema::postgres::discovery] TableConstraintsQueryResult
{
  constraint_schema: "public",
  constraint_name: "event_stream_ordering_fkey",
  table_schema: "public",
  table_name: "current_state_events",
  constraint_type: "FOREIGN KEY",
  is_deferrable: "NO",
  initially_deferred: "NO",
  check_clause: None,
  column_name: Some("event_stream_ordering"),
  ordinal_position: Some(1),
  position_in_unique_constraint: Some(1),
  unique_constraint_schema: None,
  unique_constraint_name: None,
  match_option: None,
  update_rule: None,
  delete_rule: None,
  referential_key_table_name: None,
  referential_key_column_name: None
}
[2024-01-29T12:48:56Z DEBUG sea_schema::postgres::discovery] Unique(Unique { name: "current_state_events_room_id_type_state_key_key", columns: ["room_id", "type", "state_key"] })

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/postgres/parser/table_constraints.rs:52:63

[tyt2y3]

Please provide the schema in SQL, and there's some fix in SeaSchema lately, it might have been resolved?

[avdb13]

Yes, I stopped reading from the database and switched to communication over a REST API.
I eventually managed to solve the issue by dropping the problematic keys.

[Patrick-Lehner-Woven-by-Toyota]

We are also seeing this issue with any sea-orm-cli version that uses sea-schema 0.14.2 (sea-schema 0.14.0 works).

We still need to work out a minimum reproduction, but opened SeaQL/sea-schema#130 for now.

[Patrick-Lehner-Woven-by-Toyota]

We found a small schema that reproduces the issue, a script to create it is now included in SeaQL/sea-schema#130