hey john,
what database are you using?
please give us the output of EOAdaptorDebuggingEnabled.
i had a problem with postgresql. the adaptor was not able to fetch
the abstract entity. it always tried to fetch a NULL table (no table
name in the eomodel).
so i patched the postgresql-adaptor and
Thanks to both of you for your response.I have double check and rechecked and I'm still having the same problem. I rebuilt the relationship to the abstract entity again to no avail. I have double checked for overridden methods that didn't call super. I believe that I was hasty in my previous con
I am so ashamed.
Since I was changing so many objects at once I made a check list to
walk through to make sure that I caught as many things as I could.
Apparently I forgot one.
Though I used the createsubclass menu item to minimize the risk of
typos, forgotten relationships, etc. I didn'
I checked and double checked. I tried leaving the abstract table's
name blank and marking it as read only because that's what the
example did in the horizontal example with the abstract objects.
Same thing.
When I did this change, I made 8 entities abstract and created 23
subclasses. N
If only there was an EOModeler coming soon that did not do this ...On Jul 18, 2006, at 5:42 PM, Robert Walker wrote:When this happens the only workaround I can find is to manually edit the .plist file. ___
Do not post admin requests to the list. They
John,
Check the model, especially for the abstract entity to ensure that it
is not missing any table or column names. That is a common source of
this problem.
Chuck
On Jul 18, 2006, at 4:06 PM, John Larson wrote:
Thanks to both of you for your response.
I have double check and recheck
John,I've used inheritance before and not had any problem, but if was from scratch. In this case I have changed an existing model. IMHO it just seems like eomodeler isn't cleaning something out after I changed the model.I wouldn't be terribly surprised at that, but the only issue I'm aware of wit
On Jul 18, 2006, at 10:27 AM, John Larson wrote:
Since I originally posted this, I redid the entire model and db to
use horizontal inheritance (which is actually better for the
application's purposes anyhow). The problem du jour is that the to-
many relationships that have the abstract par
Thanks for your reply Robert,I consulted the example and the eomodeler user guide, just to be sure, and everything looks fine.The problem is with relationships to the superclass from other entities. What I am doing is calling invoice.toLines() and expecting to get an NSArray of InvoiceLine (the su
John,Have you inspected the WOInheritanceExample project, located in /Developer/Examples/JavaWebObjects? This project contains the same model using Vertical Mapping, Horizontal Mapping, and Single Table Mapping. Check this design against your model and see if you can find any configuration issues
Since I originally posted this, I redid the entire model and db to
use horizontal inheritance (which is actually better for the
application's purposes anyhow). The problem du jour is that the to-
many relationships that have the abstract parent class as the
destination don't fire their faul
I just got done with a wholesale change to a model where I made a
table abstract and implemented vertical inheritance in subclassed
tables. That part seems to have gone fine. The problem is that the
parent class (the abstract class) is the destination entity in a to-
many relationship from
12 matches
Mail list logo
