yes... basically, after you've created your EO from the EOModeler, add your
attribute into the code that it creates.
eg. (added code)
-----------------------------------------------
String fullName;
/**
* Returns the value of fullName
*
* @return the value of fullName
*/
public String getFullName() {
String fullName;
if (middleName != null) {
fullName = firstName + " " + middleName + " " + lastName;
}
else {
fullName = firstName + " " + lastName;
}
return fullName;
}
-----------------------------------------------
At 01:57 PM Friday 3/19/99 -0800, Bill Bumgarner wrote:
>Is it possible to have attributes without on an EO without a
>corresponding column in the database?
>
>I ask because it is sometimes necessary to have completely transient
>state associated with an EO that should never be persisted.
>Unfortunately, while it is quite easy to use ObjC categories to tack on
>method implementations to an EO (I can't *believe* that Java doesn't
>have Categories or some equivalent functionality. What a horribly
>STUPID omission! I don't *want* to use file merge every time I dump
>source. DUH!).... one cannot add ivars to a class from a category.
>
>I really want a situation where the automatically generated code is
>isolated in one set of files and the hand written stuff in another
>set... this greatly reduces maintenance costs and riskful tedium in the
>development process.
>
>Anyone know of an effective means to do this?
>
>Some perverse set of subclassing????
>
>b.bum
>
Derek Eide
Web Programmer
EyeWire, Inc. ( http://www.eyewire.com )
(403) 750-4297
