kiya-abdulahi commented 10 months ago

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

I have a relationship between tables that looks something like this:

CREATE TABLE "event" (
  "id" serial PRIMARY KEY,
  "slug" VARCHAR NOT NULL,
   .....a few more columns,
);

CREATE TABLE "product" (
  "id" serial PRIMARY KEY,
  "event_id" int UNIQUE NOT NULL,
  .....a few more columns,
);

CREATE INDEX ON "product" ("event_id");
ALTER TABLE "product" ADD FOREIGN KEY ("event_id") REFERENCES "event" ("id") ON DELETE CASCADE;

I then query my event table by slug and join on product as such:

const { data: event, error } = await db
      .from('event')
      .select('*, product(*)')
      .eq('slug', slug)
      .single()

Now my event with a single product should be returned. When I try to target my event doing the following:

const product = event?.product

Product typing comes back as an array. But when I log the product to my console, i see its not an array but indeed a single product object. This is causing my typings to be incorrect.

Is there something im missing in regards to joins that explains this behavior? Or perhaps my tables are incorrect?

Expected behavior

Expect product to not be an array but an object.

Screenshot

The screenshot shows that when hovering over event?.product, it indicates it's an array. But when I log event?.product, you can see in my terminal that it's not an array but its an object.