strapi-plugin-navigation: Problem with 2.0.9 pagination and postgresql
I just tried 2.0.9 and I’m getting this error in the backend logs when I try to access the frontend
[2022-03-28 15:53:04.325] error: select "t0".* from "navigations" as "t0" limit $1 - LIMIT must not be negative
error: select "t0".* from "navigations" as "t0" limit $1 - LIMIT must not be negative
at Parser.parseErrorMessage (/home/cortopy/code/disruptor/cms/node_modules/pg-protocol/dist/parser.js:287:98)
at Parser.handlePacket (/home/cortopy/code/disruptor/cms/node_modules/pg-protocol/dist/parser.js:126:29)
at Parser.parse (/home/cortopy/code/disruptor/cms/node_modules/pg-protocol/dist/parser.js:39:38)
at Socket.<anonymous> (/home/cortopy/code/disruptor/cms/node_modules/pg-protocol/dist/index.js:11:42)
at Socket.emit (node:events:520:28)
at Socket.emit (node:domain:475:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at Socket.Readable.push (node:internal/streams/readable:228:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
I’m using PostgreSQL 13
This wasn’t happening with earlier versions, so I suspect the problem lies in the changes done in https://github.com/VirtusLab-Open-Source/strapi-plugin-navigation/pull/185/files#diff-9ba71205ff2062647c32f47eebb1243330e0e2774f4f49bb26ab84644cb1c52f
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 21 (11 by maintainers)
Commits related to this issue
- fix: issues #192 #189 disappearing single types — committed to VirtusLab-Open-Source/strapi-plugin-navigation by cyp3rius 2 years ago
- fix: issues #192 #189 disappearing single types (#193) — committed to VirtusLab-Open-Source/strapi-plugin-navigation by cyp3rius 2 years ago
I’ve fixed error from your latest posts in
v2.0.12
and forced saving Single Types relations withid: 1
as seems on some MySQL drivers it wasn’t working by default.Jeez, must grab a beer then 😃 The trickiest case with Strapi I ever had. Closing this one, thanks for cooperation @Kinbaum 👍
Yep, Thats not compatible with v3 approach, do not update to v2.0.9.
I how to take it and fix by night today.