Drizzle TeamDT
Drizzle Team•3y ago
focused_morning

Help, issue that will drop our user table

We generated and pushed our schemas to a dev branch in planetscale, and then deployed that branch no issue. One of the schemas was the User schema. We added two schemas to our db and pushed to dev again, no changes were made to the User schema, yet pushing to the dev db wants to truncate our user table because of the createdAt and updatedAt columns. What is happening and what should we do?

Schema
export const user = mysqlTable(
    'User',
    {
        id: varchar('id', { length: 191 }).primaryKey().notNull(),
        username: varchar('username', { length: 191 }),
        profileImageUrl: varchar('profileImageUrl', { length: 191 }),
        email: varchar('email', { length: 191 }),
        bio: text('bio'),
        headline: text('headline'),
        website: varchar('website', { length: 191 }),
        twitter: varchar('twitter', { length: 191 }),
        instagram: varchar('instagram', { length: 191 }),
        opensea: varchar('opensea', { length: 191 }),
        membershipTier: mysqlEnum('membershipTier', [
            'COMMON',
            'RARE',
            'EPIC',
            'LEGENDARY',
            'PN',
        ]),
        role: mysqlEnum('role', ['ADMIN', 'CREATOR', 'USER'])
            .default('USER')
            .notNull(),
        createdAt: datetime('createdAt', { mode: 'string', fsp: 3 })
            .default(sql`(CURRENT_TIMESTAMP(3))`)
            .notNull(),
        updatedAt: datetime('updatedAt', { mode: 'string', fsp: 3 })
            .default(sql`(CURRENT_TIMESTAMP(3))`)
            .notNull(),
    },
    (table) => {
        return {
            usernameIdx: index('User_username_idx').on(table.username),
            usernameKey: uniqueIndex('User_username_key').on(table.username),
        }
    },
)
Was this page helpful?