[
https://issues.apache.org/jira/browse/OPENJPA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-143:
Fix Version/s: 0.9.7
> Problems with Single Table Inheritance Strategy (and Discrimina
Problems with Single Table Inheritance Strategy (and Discriminator Type of
Integer)
---
Key: OPENJPA-143
URL: https://issues.apache.org/jira/browse/OPENJPA-143
Project
That sounds like a good idea, but rather than adding a new
"StrategyClass" annotation, why not just add a "strategyClass"
element to the existing "Strategy" annotation?
On Oct 31, 2006, at 1:28 AM, Patrick Linskey wrote:
Hi,
@Strategy allows the specifica
> > @Strategy allows the specification of a custom class name in string
> > form. However, class names inside quotes don't refactor all that
> > well. I
> > think we should add an @StrategyClass annotation that allows
> > specification of a strongly-typed Cl
@Strategy allows the specification of a custom class name in string
form. However, class names inside quotes don't refactor all that
well. I
think we should add an @StrategyClass annotation that allows
specification of a strongly-typed Class instance. What say ye?
I'm not voting
Hi,
@Strategy allows the specification of a custom class name in string
form. However, class names inside quotes don't refactor all that well. I
think we should add an @StrategyClass annotation that allows
specification of a strongly-typed Class instance. What say ye?
We should make a si
