Hi Dan,
Sorry. I will expand a bit on this: I use a class 'ProfileElement' parent of several specified classes like ProfileElementText, ProfileElementNumeric etc etc. The ProfileElement class is the one with the 'SUPERCLASS_TABLE". This worked fine for me, until recently I added to new subclasses [1] and [2]. All the sudden - when adding the fixtures - my app freezes without throwing an error or something. (I tried several implementations on several machines: all the same result) I retried with different types etc etc but to no avail. I cannot find anything in my code that is different from what I used to do with the other subclasses... So I wonder: Are there any known limitations to using a Superclass table? Like you cannot add columns to a table that has data already? (I think I noticed that columns are added to the superclass table on the moment a first persistence takes place..) Or anything else that I miss? Or anything you can detect? By implementing the work-a-round everything works as expected again. Grtz Johan [1] https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Profile/ProfileElementTimePeriod.java [2] https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Profile/ProfileElementUseTimePeriod.java On 19 February 2015 at 13:28, wrote: > After some further reseach I found out that the used types do not matter. > My work-a-round now is to put the properties on the parent-object and hide > them except on the subclasses intended. > > > glad you have a workaround, at least? > > Are there any known limits that I miss? > > Or can columns only be added to empty tables or ...? > > Not sure I understand your question... can you rephrase/expand? thx Dan
