Skip to content

Tag: sql

1:n disable constraints for the n-side?

The Problem I have a 1:n relation, but the n side shouldnt rely on constraints. So i actually wanna insert a EntityPojo via its future id, when its not saved yet ( Lets ignore that its a bad practice ). This looks kinda like this. Cascading is not possible here, i only have its future ID, not a reference to

jOOQ – DefaultRecordMapper – List

Can the DefaultRecordMapper handle lists? Model example (really getter/setter are used): I first tried it with a simple select: Also I have tried using the nested syntax but it didn’t work: The list never gets initialized. I am unsure if I could be doing something wrong. Is this possible with the Defaul…