You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INFO Applied foreign key for relationship after historic resync complete: table - lensgameindexer_lens_game.game_created constraint - fk_player_joined_game_id
21 December - 14:49:14.779469 INFO Applied index for relationship after historic resync complete: table - lensgameindexer_lens_game.game_created index - idx_game_created_game_id
21 December - 14:49:14.784115 INFO Applied unique constraint key for relationship after historic resync complete: table - lensgameindexer_lens_game.game_started constraint - unique_game_started_game_id
21 December - 14:49:14.786004 INFO Applied foreign key for relationship after historic resync complete: table - lensgameindexer_lens_game.game_created constraint - fk_game_started_game_id
Error starting the server: Could not apply relationship - PgError db error: ERROR: relation "idx_game_created_game_id" already exists
We need a way to:
a. either rename these relationships in yaml
b. automatically support renaming of duplicate indices / relationships
I think that a) would be preferable, since it would also allow us to specify custom names of the graphql relationship. This would make the API more readable in cases where event-input-name is not a good indicator for the name of the relationship.
The text was updated successfully, but these errors were encountered:
Currently you cannot add multiple relationships that have the same input name. Example:
rindexer.yaml
This leads to duplication errors in postgres:
We need a way to:
a. either rename these relationships in yaml
b. automatically support renaming of duplicate indices / relationships
I think that a) would be preferable, since it would also allow us to specify custom names of the graphql relationship. This would make the API more readable in cases where event-input-name is not a good indicator for the name of the relationship.
The text was updated successfully, but these errors were encountered: