Transactions & DB caching in Prisma

viperfx · November 10, 2020, 8:40pm

I am running into an issue, where writes to the DB are not showing up after a navigate call. But do show up on a manual refresh.

I have the following getCurrentUser code - see getCurrentUser method

gist.github.com

https://gist.github.com/viperfx/55a0055bb31f997d006e0b20edb177ff#file-getcurrentuser-js

feedbackPage.js

const FeedbackPage = ({id}) => {
  const { logIn, logOut, isAuthenticated, currentUser  } = useAuth()
  let { filter } = useParams()
  const { addMessage } = useFlash()
  return (
    <CoreLayout>
      <PageHeader title={"Feedback"}/>
      <div class="px-4 mt-6 sm:px-6 lg:px-8">
        <FeedbackListCell teamId={currentUser.currentTeam.id} filter={filter}/>
      </div>

This file has been truncated. show original

getCurrentUser.js

export const getCurrentUser = async (decoded, { _token, _type }) => {
  const account = await db.user.findOne(
    {
      where: {sub: decoded.sub},
      include: {
        currentTeam: true
      }
    },
  )
  if (!account) {

This file has been truncated. show original

pickTeamPage.js


const CREATE_CONTACT = gql`
  mutation CreateTeamWithNameMutation($input: CreateTeamInput!) {
    createTeamWithName(input: $input) {
      id
      name
    }
  }
`
const PickTeamPage = () => {

This file has been truncated. show original

There are more than three files. show original

If the user does not have a team, I am directing them to a pickTeam page. On this team page, after onCompleted of the mutation, I am navigation to a page. After the redirect to the page, the currentUser method returns an empty team, even though it was just created by Prisma.

Ive tried doing delays with await new Promise(r => setTimeout(r, 1000)); but it does not help.

The currentUser.currentTeam returns null after navigate, but returns an object after a browser refresh.

Why is this happening? is this caching on prisma? or RW caching the currentUser data?

My current workaround is to do a window.location.reload()

forresthayes · November 11, 2020, 2:20pm

It may be caching in Apollo client.

I think the cache is updated based on the fields you select for return in your mutation. In your case, the createTeamWithName mutation selects only the id and name of the new Team, but have you tried to select the related owner/user? If you can, I think it might update the currentUser as cached with the newly picked/created team record.