Nick Schot

For the last 2 points we still need some reliable reproduction. I encountered it often but have not yet been able to reliably reproduce. Likely timing/lock issue in the watcher.

Fix is in #737

This is caused by `formatString` in `/src/packages/server/request/parser/utils/format.js`which splits on `,` in all cases. @zacharygolba why is this so? What data type as a value in the query parameters should be...

~~This issue is not encountered when QP's not defined by Lux are used (i.e. `search[name]=my, search term`~~ Just checked, the issue is also there for custom QP's.

I am now thinking this error is caused by something (presumably lux) parsing the nextVal function into a string causing Postgres to error.

This problem also exists with the update hasOne relationship.

~~See #739 , the "fix" proposed in this PR is not really desirable.~~

PR has been updated with a new and much better fix.

This kind of blows up the amount of queries that are happening. Needs either a perf improvement or the use of relationship links instead of adding all relationship id's.

Any ideas are welcome @zacharygolba . I can make a PR if you approve of the solution. I'm still a bit in doubt whether or not to make the assumption...