github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #2387] verification table: value too long for type character varying(255) #9175

New Issue
Closed
opened 2026-04-13 04:32:34 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-13 04:32:34 -05:00
Owner
Copy Link

Originally created by @afrokick on GitHub (Apr 21, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2387

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

I'm trying to implement linkSocial API, but get this PG error:

error: value too long for type character varying(255)

I've started digging how it works:

  1. https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/api/routes/account.ts#L167

linkSocial endpoint calls generateState function with email and userId.

  1. https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/oauth2/state.ts#L21

generateState function creates a string via JSON.stringify. This string is more than 255 characters.

An example of test object(322 characters):

JSON.stringify({
		callbackURL:'',
		codeVerifier:'CVL1rHarg4buiN56D4Q43zW23m8Kaqp6wMUZRVjqefqntciFqu5BR29GRyBpHHDZ1AFHzQYMhtKbY6bv5aVx7WFpXJHn8wjh3DeFPWXhT6ynLjqX4XeCPu7iXFrUkSMa',
		errorURL: '',
		newUserURL: '',
		link: {
				email:'myemail@test.com',
				userId:'VKBFSCDMURZNXDMLOCAEVKBEQATVFKCA'
		},
		expiresAt: Date.now() + 10 * 60 * 1000,
		requestSignUp: false
})
  1. I've checked the database and realised that verification.value column has a max 255char size.

It can be manually fixed by increasing column size for verification.value column, but it would be nice to have a good default size for this column.

Current vs. Expected behavior

Values with more than 255 chars should work without database errors.

What version of Better Auth are you using?

1.2.3

Provide environment information

- bun 1.2
- Postgres 16

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

Additional context

No response

Originally created by @afrokick on GitHub (Apr 21, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2387 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce I'm trying to implement linkSocial API, but get this PG error: ``` error: value too long for type character varying(255) ``` I've started digging how it works: 1. https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/api/routes/account.ts#L167 linkSocial endpoint calls generateState function with email and userId. 2. https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/oauth2/state.ts#L21 generateState function creates a string via JSON.stringify. This string is more than 255 characters. An example of test object(322 characters): ``` JSON.stringify({ callbackURL:'', codeVerifier:'CVL1rHarg4buiN56D4Q43zW23m8Kaqp6wMUZRVjqefqntciFqu5BR29GRyBpHHDZ1AFHzQYMhtKbY6bv5aVx7WFpXJHn8wjh3DeFPWXhT6ynLjqX4XeCPu7iXFrUkSMa', errorURL: '', newUserURL: '', link: { email:'myemail@test.com', userId:'VKBFSCDMURZNXDMLOCAEVKBEQATVFKCA' }, expiresAt: Date.now() + 10 * 60 * 1000, requestSignUp: false }) ``` 3. I've checked the database and realised that `verification.value` column has a max 255char size. It can be manually fixed by increasing column size for `verification.value` column, but it would be nice to have a good default size for this column. ### Current vs. Expected behavior Values with more than 255 chars should work without database errors. ### What version of Better Auth are you using? 1.2.3 ### Provide environment information ```bash - bun 1.2 - Postgres 16 ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript ``` ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:32:34 -05:00
GiteaMirror commented 2026-04-13 04:32:36 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (May 31, 2025):

can you please share the column type of the current pg database for values ?
You should check the actual column type of verification.value in your database. Even though it's defined as text in the schema, some databases (like MySQL or SQLite) or ORMs (e.g. Prisma) may implicitly map it to VARCHAR(255) unless explicitly specified.

TEXT in most databases (e.g., PostgreSQL) can store very large values

<!-- gh-comment-id:2925749402 --> @Kinfe123 commented on GitHub (May 31, 2025): can you please share the column type of the current pg database for values ? You should check the actual column type of verification.value in your database. Even though it's defined as text in the schema, some databases (like MySQL or SQLite) or ORMs (e.g. Prisma) may implicitly map it to VARCHAR(255) unless explicitly specified. TEXT in most databases (e.g., PostgreSQL) can store very large values
GiteaMirror commented 2026-04-13 04:32:37 -05:00
Author
Owner
Copy Link

@afrokick commented on GitHub (Jun 1, 2025):

It was set to character varying(255) for verification.value. I've manually changed it to character varying(1024) to fix the problem.

I use Postgres + Knex.

<!-- gh-comment-id:2926732968 --> @afrokick commented on GitHub (Jun 1, 2025): It was set to `character varying(255)` for `verification.value`. I've manually changed it to `character varying(1024)` to fix the problem. I use Postgres + Knex.
GiteaMirror commented 2026-04-13 04:32:38 -05:00
Author
Owner
Copy Link

@SkidGod4444 commented on GitHub (Jun 25, 2025):

It was set to character varying(255) for verification.value. I've manually changed it to character varying(1024) to fix the problem.

I use Postgres + Knex.

how you did this can you pls guide? am using supabase @afrokick

<!-- gh-comment-id:3004086029 --> @SkidGod4444 commented on GitHub (Jun 25, 2025): > It was set to `character varying(255)` for `verification.value`. I've manually changed it to `character varying(1024)` to fix the problem. > > I use Postgres + Knex. how you did this can you pls guide? am using supabase @afrokick
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#9175
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?