github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #177] bug: MongoDB Adapter does not use plural collection name by default #16791

New Issue
Closed
opened 2026-04-15 14:46:29 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-15 14:46:29 -05:00
Owner
Copy Link

Originally created by @Iulian-Dragomirescu on GitHub (Oct 15, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/177

I encountered an issue with the Mongoose adapter where it does not automatically use the plural form of the collection name. When I try to access the Account model using await Account.findOne(), I receive an empty array

const accountSchema = new mongoose.Schema({
  id: { type: String, required: true, unique: true },
  userId: { type: String, required: true, ref: "User" },
  accountId: { type: String, required: true },
  providerId: { type: String, required: true },
  accessToken: { type: String },
  refreshToken: { type: String },
  expiresAt: { type: Date },
  password: { type: String },
});

export const Account = mongoose.model("Account", accountSchema);

Attempt to fetch an account:

const account = await Account.findOne();

I receive an empty array when accessing await Account.findOne()

When using the following configuration with BetterAuth:

const client = mongoose.connection

export const auth = betterAuth({
  database: mongodbAdapter(client),
  emailAndPassword: {
    enabled: true,
  },
  user: {
    modelName: "users",
  },
  session: {
    modelName: "sessions",
  },
  account: {
    modelName: "accounts",
  },
  verification: {
    modelName: "verifications",
  },
});

The problem is resolved, but it should ideally work without the need to specify the model name in plural form

I believe the adapter should default to using the plural form of the model name without requiring explicit configuration for the collection name

Originally created by @Iulian-Dragomirescu on GitHub (Oct 15, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/177 I encountered an issue with the Mongoose adapter where it does not automatically use the plural form of the collection name. When I try to access the Account model using `await Account.findOne()`, I receive an empty array ``` const accountSchema = new mongoose.Schema({ id: { type: String, required: true, unique: true }, userId: { type: String, required: true, ref: "User" }, accountId: { type: String, required: true }, providerId: { type: String, required: true }, accessToken: { type: String }, refreshToken: { type: String }, expiresAt: { type: Date }, password: { type: String }, }); export const Account = mongoose.model("Account", accountSchema); ``` Attempt to fetch an account: ``` const account = await Account.findOne(); ``` I receive an empty array when accessing `await Account.findOne()` When using the following configuration with BetterAuth: ``` const client = mongoose.connection export const auth = betterAuth({ database: mongodbAdapter(client), emailAndPassword: { enabled: true, }, user: { modelName: "users", }, session: { modelName: "sessions", }, account: { modelName: "accounts", }, verification: { modelName: "verifications", }, }); ``` The problem is resolved, but it should ideally work without the need to specify the model name in plural form I believe the adapter should default to using the plural form of the model name without requiring explicit configuration for the collection name
GiteaMirror added the locked label 2026-04-15 14:46:29 -05:00
GiteaMirror commented 2026-04-15 14:46:32 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Oct 16, 2024):

does mongo always use plural form collection names?

<!-- gh-comment-id:2417326864 --> @Bekacru commented on GitHub (Oct 16, 2024): does mongo always use plural form collection names?
GiteaMirror commented 2026-04-15 14:46:33 -05:00
Author
Owner
Copy Link

@Iulian-Dragomirescu commented on GitHub (Oct 16, 2024):

in mongoose yes: The first argument is the singular name of the collection your model is for. Mongoose automatically looks for the plural, lowercased version of your model name. Thus, for the example above, the model Tank is for the tanks collection in the database..
I personally did not use mongo directly, only through mongoose

<!-- gh-comment-id:2417569632 --> @Iulian-Dragomirescu commented on GitHub (Oct 16, 2024): in mongoose yes: `The first argument is the singular name of the collection your model is for. Mongoose automatically looks for the plural, lowercased version of your model name. Thus, for the example above, the model Tank is for the tanks collection in the database.`. I personally did not use mongo directly, only through mongoose
GiteaMirror commented 2026-04-15 14:46:34 -05:00
Author
Owner
Copy Link

@csyedbilal commented on GitHub (Oct 17, 2024):

Prisma Adapter is supported for MongoDB??

<!-- gh-comment-id:2420004302 --> @csyedbilal commented on GitHub (Oct 17, 2024): Prisma Adapter is supported for MongoDB??
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#16791
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?