User-defined columns in CamelCase stop realtime from sending updates

[NiklasPor]

Bug report

User-defined columns in CamelCase stop realtime from sending updates to the client.

• Related bug from the past: Realtime does not work for tables with User-defined fields #211
• Related discord discussion
• Only happens on remote environments, not if you're using the CLI / docker environment

Describe the bug

When a table contains a user-defined field with CamelCase naming, realtime stops sending updates for the table.

To Reproduce

CREATE TYPE "public"."ProjectStatus" AS ENUM (
    'Available',
    'Archived',
    'Deleted'
);

CREATE TABLE "public"."Project" (
    "id" "uuid" DEFAULT "extensions"."uuid_generate_v4"() NOT NULL,
    "name" character varying NOT NULL,
    "status" "public"."ProjectStatus" DEFAULT 'Available'::"public"."ProjectStatus" NOT NULL
);

  supabase
    .channel('*')
    .on('postgres_changes', { event: '*', schema: '*' }, (payload) => console.log(payload))
    .subscribe();

Result:

• Logs don't show anything
• WebSocket inspector is also not showing anything

Workaround

Renaming the types to snake_case fixes the problem and supabase sends updates again:

ALTER TYPE public."EntityStatus" RENAME TO entity_status;

System information

• OS: macOS
• Supabase CLI: 1.8.7 (bug is not occuring there, only on remote)
• supabase-js: 2.0.0

Additional context

As stated at the beginning, a very similar / same bug already appeared in the past: #211

[w3b6x9]

@NiklasPor thanks for creating this bug report! i'll investigate this shortly.

[w3b6x9]

@NiklasPor i was able to reproduce. i'll pass this on to the rest of the realtime team and we'll address this. thanks again!

[w3b6x9]

Note: doesn't work when there's any uppercase letter in the type name.

[w3b6x9]

@NiklasPor we have just deployed a fix so this shouldn't be an issue anymore.

[NiklasPor]

Wow, thanks a lot!