ambiguous column name: value when running prisma studio
ORM
so prisma v7 new studio aggregates data into value column
with "count" as (select cast(coalesce(count(*), 0) as text) as "value" from "public"."verification" where true) select "value", "identifier", "id", "updatedAt", "createdAt", "expiresAt", "count"."value" as "__ps_count__" from "public"."verification", "count" where true limit $1 offset 0
with "count" as (select cast(coalesce(count(*), 0) as text) as "value" from "public"."verification" where true) select "value", "identifier", "id", "updatedAt", "createdAt", "expiresAt", "count"."value" as "__ps_count__" from "public"."verification", "count" where true limit $1 offset 0
which makes me unable to use default column name "value" shouldn't all internal column names be with _ or something to not clash common wording? i was using better-auth whose verification table has value column that stores otp and other value for auth. github issue here https://github.com/prisma/prisma/issues/28675
Bug description setup better auth 1.4.0 with prisma v7 and genrate schema db push and all and open prisma studio console throws error in studio with "count" as (select cast(coalesce(count...