使用 N 到 M 个恐慌查询 想法另一个观察:

如何解决使用 N 到 M 个恐慌查询 想法另一个观察:

重现步骤

日志

  prisma-client { clientVersion: '2.13.1' }  
  prisma-client Error: PANIC: 1
  prisma-client 
  prisma-client This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.
  prisma-client 
  prisma-client https://github.com/prisma/prisma-client-js/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v12.18.3+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+undefined%7C%0A%7C+Prisma+Client+++%7C+2.13.1+++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0A++prisma-client+%7B+clientVersion%3A+%272.13.1%27+%7D++%0A%60%60%60&title=PANIC%3A+1&template=bug_report.md
  prisma-client 
  prisma-client If you want the Prisma team to look into it,please open the link above ?
  prisma-client 
  prisma-client     at NodeEngine.handleRequestError (C:\Users\TreNr\AppData\Roaming\Prisma\Studio\e5cd9139\runtime\index.js:26642:21)
  prisma-client     at C:\Users\TreNr\AppData\Roaming\Prisma\Studio\e5cd9139\runtime\index.js:27295:36
  prisma-client     at processTicksAndRejections (internal/process/task_queues.js:97:5)
  prisma-client     at async PrismaClientFetcher.request (C:\Users\TreNr\AppData\Roaming\Prisma\Studio\e5cd9139\runtime\index.js:78094:24)
  prisma-client     at async X:\dev\familytreebackend\node_modules\@prisma\cli\build\index.js:104367:25
  prisma-client     at async X:\dev\familytreebackend\node_modules\@prisma\cli\build\index.js:104350:22
  prisma-client     at async Photon.request (X:\dev\familytreebackend\node_modules\@prisma\cli\build\index.js:104391:34)
  prisma-client     at async PhotonService.respond (X:\dev\familytreebackend\node_modules\@prisma\cli\build\index.js:104569:38)
  prisma-client     at async Object.StudioServer2.onWSMessage [as callback] (X:\dev\familytreebackend\node_modules\@prisma\cli\build\index.js:104717:29)  +30s
  prisma-client { clientVersion: '2.13.1' }  +5s
  1. 使用婚姻和用户之间的 n 到 m 关系创建数据库架构
...
model User {
  id         Int        @id @default(autoincrement())
  forename   String
  lastname   String
  marriages  Marriage[]
}

model Marriage {
  id    Int    @id @default(autoincrement())
  users User[]
}
  1. 迁移并启动工作室
npx prisma migrate dev --preview-feature
npx prisma studio
  1. 创建 2 个用户并在他们之间建立婚姻

  2. 查询用户

出现以下错误 https://github.com/prisma/prisma-client-js/issues/955

想法

似乎与prisma.user.findMany()有直接关系。

用作查询时

    Query: {
        users: (_,__,context) => {
            const pc: PrismaClient = context.prisma;
            return pc.user.findMany({ include: { marriages: true } });
        },user: async (_,args,context) => {
            const pc: PrismaClient = context.prisma;
            const users = pc.user.findUnique({ where: { id: parseInt(args.id) },include: { marriages: true } });
            return users;
        }
    }
  • 失败
query {
  users {
    id
    marriages {
      id
    }
  }
}
  • 作品
query {
  user(id: 1) {
    id
    marriages {
      id
    }
  }
}

另一个观察:

只有在将婚姻与 findMany 结合使用时才会发生这种情况。

    users: (_,context) => {
        const pc: PrismaClient = context.prisma;
        return pc.user.findMany({ include: { marriages: true } });
    }

如果不包含没有错误。如果它包含在 findUnique 中,它也可以工作

解决方法

上面观察到的问题似乎是最新版本中的一个错误。

详情:https://github.com/prisma/prisma-client-js/issues/955

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-