Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is it bad to put Objects in EO derived classes




On Oct 31, 2006, at 8:51 AM, Baiss Eric Magnusson wrote:

I need to add a BigDecimal to each Transaction record, I added it to
	public class Transaction extends EOGenericRecord
as a local object. I don't instantiate it until it is needed.

My question is, even though it is transient, is it better to add it to the base EOModel, so it exists in the DB?

I've read that it is bad to put Objects in EO derived classes.

If I understand correctly, this is just a cached valued used for optimization. It is not intended to be stored in the DB? I do this frequently for optimization and have seen no problems _provided that_ you are aware that EOF will update the underlying values and thus render this value inaccurate. This can be handled by watching for certain method calls into your EO from EOF and invalidating this value when they happen. I am pressed for time at the moment, so I can't go into details. I will attach example code that shows what to do (and much more).


Chuck

Attachment: GenericRecord.java
Description: Binary data

--

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:
http://lists.apple.com/mailman/options/webobjects-dev/email@hidden

This email sent to email@hidden

References: 
 >Is it bad to put Objects in EO derived classes (From: Baiss Eric Magnusson <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.