onConflictDoNothing still incrementing primaryKey
I have the following ballots schema and then inserting to it via an Next.js app directory API route. I added not to do anything if there is a conflict. I thought I was doing it correctly as nothing was being inserted into the DB. However, when I inserted a new record and refreshed Supabase, I all of a sudden went from a primary key of 1 for the first record to a primary key of 8 for the 2nd record. Is there a way to not increment this primary key if there is a conflict? Am I possibly doing some checks wrong?
