8 replies

Updating name/username in DB directly

Database related🤔Question✅Solved

Hi, I'm sorry in advance for my bad English. I have a question regarding name/username update.

I want to implement an API for updating the user's info, which includes better-auth's "user" and my custom "userProfile" tables. Is this ok to directly update name and username in the "user" table or it's not recommended? If the latter, what would be a better approach? Thank you!

 await db.transaction(async (trx) => {
         await trx
           .update(userProfile) // custom table
           .set({
             country: body.country,
             bio: body.bio,
             updatedAt: new Date(),
           })
           .where(eq(userProfile.userId, userId));
         await trx
           .update(user) // better-auth table
           .set({
             username: body.username,
             name: body.name,
             updatedAt: new Date(),
           })
           .where(eq(user.id, userId));
 });

 await db.transaction(async (trx) => {
         await trx
           .update(userProfile) // custom table
           .set({
             country: body.country,
             bio: body.bio,
             updatedAt: new Date(),
           })
           .where(eq(userProfile.userId, userId));
         await trx
           .update(user) // better-auth table
           .set({
             username: body.username,
             name: body.name,
             updatedAt: new Date(),
           })
           .where(eq(user.id, userId));
 });

Solution

It depends on if your using secondary storage, cookie caching, and if you're using the built-in session fetching endpoints

With secondary storage, it also stores the session (including user context, like the name) in secondary storage, and that'll be used before hitting your database

With cookie caching, it does the same as above but in the cookie, and that'll be used before hitting your secondary storage/database

Using the built-in api endpoints to update your username also updates the session in secondary storage/cookie (can obviously only update the cookie that's made the request), so that solves that problem.

If you don't have secondary storage, and have disabled cookie caching, then I can't see any reasons this will cause a problem - if either of the above are enabled however, you'll also need to update them, if you want to use the built in api.getSession to return your user data, for example

Jump to solution

Updating name/username in DB directly

Database related🤔Question✅Solved

 await db.transaction(async (trx) => {
         await trx
           .update(userProfile) // custom table
           .set({
             country: body.country,
             bio: body.bio,
             updatedAt: new Date(),
           })
           .where(eq(userProfile.userId, userId));
         await trx
           .update(user) // better-auth table
           .set({
             username: body.username,
             name: body.name,
             updatedAt: new Date(),
           })
           .where(eq(user.id, userId));
 });

 await db.transaction(async (trx) => {
         await trx
           .update(userProfile) // custom table
           .set({
             country: body.country,
             bio: body.bio,
             updatedAt: new Date(),
           })
           .where(eq(userProfile.userId, userId));
         await trx
           .update(user) // better-auth table
           .set({
             username: body.username,
             name: body.name,
             updatedAt: new Date(),
           })
           .where(eq(user.id, userId));
 });

Solution

Jump to solution

Updating name/username in DB directly

Updating name/username in DB directly

Similar Threads

Similar Threads

Similar Threads