Better Auth•3w ago

Schema adjustment not being reflected.

Hi guys, I'm hoping someone may be able to give me hand with this, I'm 90% confident I'm missing an extra step here or something. I have a /schemas/ folder, with multiple different files and an entry index.ts which exports * from the different files. Inside my auth.ts file, I have the drizzleAdapter, and I pass in the schemas like so:

import * as schema from "~/server/schema";

// ...rest of config

  database: drizzleAdapter(db, {
    provider: "pg",
    schema: {
      ...schema
    },
  }),

import * as schema from "~/server/schema";

// ...rest of config

  database: drizzleAdapter(db, {
    provider: "pg",
    schema: {
      ...schema
    },
  }),

One of the schemas I have defined is named under auth.ts. It includes the user and the session tables. This is what the session table looks like:

export const session = pgTable("session", {
  id: text("id").primaryKey(),
  expiresAt: timestamp("expires_at").notNull(),
  token: text("token").notNull().unique(),
  createdAt: timestamp("created_at").notNull(),
  updatedAt: timestamp("updated_at").notNull(),
  ipAddress: text("ip_address"),
  userAgent: text("user_agent"),
  userId: text("user_id")
    .notNull()
    .references(() => user.id, { onDelete: "cascade" }),
  impersonatedBy: text("impersonated_by"),
  activeOrganizationId: text("active_organization_id"),
});

export const session = pgTable("session", {
  id: text("id").primaryKey(),
  expiresAt: timestamp("expires_at").notNull(),
  token: text("token").notNull().unique(),
  createdAt: timestamp("created_at").notNull(),
  updatedAt: timestamp("updated_at").notNull(),
  ipAddress: text("ip_address"),
  userAgent: text("user_agent"),
  userId: text("user_id")
    .notNull()
    .references(() => user.id, { onDelete: "cascade" }),
  impersonatedBy: text("impersonated_by"),
  activeOrganizationId: text("active_organization_id"),
});

After making these changes, I have ran npm run db:generate as well as npm run db:push. When navigating to local.drizzle.studio I can see the extra columns created under the session table. However, when I use getSession or the database hooks to manipulate the session object, when I hover over the object I see the following structure (Image attached). Does anyone know how I should go about aligning the better auth types with my DB structs? Thanks

11 Replies

Better Auth•3w ago

Hi there! I'm Better Auth Bot. Here are some common Better Auth topics and best practices our community has been discussing: 1. Social and OAuth Providers:
Many developers ask how to set up various social login providers. Better Auth now supports providers like Google, LINE, Kakao, Naver, and even experimental support for 42 (École 42) authentication [27], [28]. For each provider, you can configure client IDs, secrets, and endpoints following our standard OAuth2 flow. Check our documentation for detailed setup instructions on each provider. 2. Passkey Plugin Enhancements:
There has been a lot of chatter about passkey sign-in improvements. Recent updates include adding client-side options like setting the authenticatorAttachment and global configurations for authenticatorSelection to enforce server-side policies [23]. Also, regarding the callbackUrl for the passkey signIn flow, earlier discussions led to its removal from docs, but we're always reviewing feedback for potential reintroduction [21]. 3. Telemetry and Runtime Compatibility:
Some users were concerned about runtime errors in non-Node.js environments. We updated the telemetry detection logic to avoid referencing process directly by safely accessing environment variables, which prevents crashes in edge and bundler scenarios [1]. 4. Admin Endpoints:
Another question is about calling admin endpoints directly from the server (e.g., in background tasks). Our recent fixes allow internal invocations that bypass some of the usual session checks while still guarding against security issues

GitHub

Build software better, together