Re: Single table inheritance and non-null attributes
Re: Single table inheritance and non-null attributes
- Subject: Re: Single table inheritance and non-null attributes
- From: Chuck Hill <email@hidden>
- Date: Thu, 30 Nov 2006 15:09:30 -0800
On Nov 30, 2006, at 2:36 PM, Clark Mueller wrote:
I'd definitely be interested... because I noticed that it does the
same thing, so I assumed there's some reason in particular that
it's done that way. :-)
In the original EOModeler it was an out and out bug. I am not sure
what is up with Entity Modeler. Maybe Mike was nostalgic for some of
the old bugs. :-P
Chuck
What's the workaround?
Thanks,
Clark
On 30 Nov 06, at 3:22 PM, Guido Neitzer wrote:
Am 30.11.2006 um 22:12 schrieb Clark Mueller:
EOModeler generates SQL that results in a table that has ALL of
the above fields defined as non-null.
This is a known problem. Mike has made a work around for the
Eclipse Entity Modeler which works fine for me. If you're
interested, send me a mail.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden