Dan Ribbens
Dan Ribbens
I don't think that this is the only thing that is preventing Payload from being instantiated more than once. I'm pretty sure there will be other issues to getting this...
This needs to be fixed for both 2.x and 3.0.
This might be related to https://github.com/payloadcms/payload/issues/5473 I am investigating this.
I think this problem is coming from drizzle-kit. I'm waiting on answers from their team.
The problem right now with schema name is that if you have other tables with the same name in other schemas they will conflict. It only works if each schema...
I pinged our drizzle friends about this, waiting on a fix.
This was fixed here: https://github.com/payloadcms/payload/pull/7453
> > When one transaction is used where multiple operations error, the result is that rollbackTransaction is called more than once. > > This sounds very strange to me. Only...
> If there are multiple operations, we must either start a transaction beforehand or have them use separate request objects (making them run in separate transactions) Yup, this is exactly...
You can handle this with a custom component on the collection. Without rewriting the relationship field you could use a type UI field that just uses form hooks to watch...