Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
RegisterColumnOverride on a table at configuration level #770
It should be at table level, so parameter required parameters are
I don't know if also a global schema column override have sense, maybe if come out with no cost yes.
Do you think is a quick feature to implement? Have you got an idea about possible snapshot release date?
I was thinking about this feature(maybe is more related to override in general). There is another requirements imho.
The idea is to run specialized queries in PA,PB,PC and cross queries in PCOMMON.
At now we have solved query generation via override, so I can run cross query in PCOMMON using i.e. CA to run queries, so resultset of PCOMMON is always in terms of CA classes.
I would like to choose if resultset in PCOMMON is of type CA, CB, CC at runtime. This is because in specialized projects i.e. in PB i would like to have CB classes not CA classes. Btw is necessary to run overrides in reverse way to map CB on CA.
What dou you think about, is it clear the issue?
Yes i use generated bean projection. At now cross query is project ed in
I've tried but is quite difficult to imagine in theory the requirement. I think I will choose dynamically the set of classes to be use on resultset writing my own external code. After this If there is new needs I'll open a new issue or pull request.