Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ability to specify the same entity name in extended entities #110

Open
haulmont-git opened this issue Dec 25, 2014 · 0 comments
Open

Ability to specify the same entity name in extended entities #110

haulmont-git opened this issue Dec 25, 2014 · 0 comments
Labels
type: enhancement New feature or request

Comments

@haulmont-git
Copy link

With some tweaks it is possible to force ORM use entity name from origin entity.

Metaclasses for original and extended entity should be merged.

It seems that migration to the new mechanism (without additional metaclass) should be mandatory for all projects. So, it will be possible to ged rid of methods such as getOriginalMetaClass.

It would eliminate necessity in fixing tickets such as: PL-3681, PL-4146, PL-1551, PL-4060, TS-8413, TS-8241, TS-8577, PL-4690, PL-3472, PL-4496, PL-4323, PL-4180, PL-3821, etc

Original issue: https://youtrack.haulmont.com/issue/PL-4682
@haulmont-git haulmont-git added cuba type: enhancement New feature or request labels Apr 27, 2018
@haulmont-git haulmont-git added this to the Undefined milestone Apr 27, 2018
@rapekas rapekas removed the cuba label Apr 27, 2018
@knstvk knstvk removed this from the Undefined milestone May 4, 2018
@jreznot jreznot modified the milestone: Undefined May 18, 2018
@knstvk knstvk removed their assignment May 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jreznot @knstvk @rapekas @haulmont-git