Use the contents of the "Column SQL" of the child column when comparing keys, enabling some cases where using a calculated key can be advantageous.
I had done a patch between two revisions, now it should be in the right format. Should I just move to peer review now? Thank you for the instructions, it's my first time using JIRA and I'm feeling lost.
welcome . it's ok to move peer review, but do you can explain more about your improvement, what's case to use it? how it advantageous?
Thank you! I've used that feature for creating a shared information between documents without creating extra tables. My use case was this:
A client wanted to create a single purchasing order after collecting all the necessary products for many projects, so I wanted to have a way to have a 1:n relationship between the C_Order and the C_Project table where I would put a percentage that how much of it was for each project. But sometimes the client want to insert or edit that information in derived documents, like invoices, receipts or payments. Then I created a virtual column that would coalesce that information at the top level.
So when a invoice was generated by a purchasing order or by itself I could still have a adequate link between that information. I can now edit the information of the order inside the invoice or having the info on the invoice alone, just by matching the key in a dynamic way. No need to have multiple tables for that.
, the explanation is still unclear for me
Closing as incomplete - the description is not enough to understand what is the requirement.