Re: Designing Batch List entries
Re: Designing Batch List entries
- Subject: Re: Designing Batch List entries
- From: Chuck Hill <email@hidden>
- Date: Mon, 26 Mar 2007 09:39:31 -0700
On Mar 23, 2007, at 12:53 PM, Ted Archibald wrote:
Hi, I'm developing a series of internal applications that focus on
bookkeeping and accounting.
Using webobjects how would one one design a simple app for batch
entries similar to what one would do in Excel? These entries could
be anywhere from 5 per batch up to 200 per batch.
Data entry could be as simple as:
Account, Amount
A-1, $10.20
A-23, $23.54
X-40 $17.25
etc.
Let's say we have an EO called Payment that consists of a PK,
Account Name and a Dollar Amount,
First off, that should almost certainly be accountFK. Let the user
enter the account name, but look it up the Acounts and make it a
proper relationship in the EO.
then another EO that contains multiples of the previous. From my
testing, if you created 200-500 empty Payment EOs, the app takes a
substantial amount of time to set each object up in memory.
How do you define "a substantial amount of time"? It should be very
fast to create those objects. Even saving 500 small objects should
be fast, though some databases are faster than others. Partly this
depends (as I recently found out from Mike) on how the JDBC adaptor
for that database implements requests for multiple new primary keys
for an entity. If it is actually taking significant time then you
are probably doing something wrong.
I've also played with creating a number of WOTextFields tied to an
array of 200-500 strings (instead of directly to an EO). The
problem I'm encountering is that this seems terribly inefficient,
slow and very non-webobjects.
I see no reason to do that. You could probably do it fairly
efficiently with POJO Payment objects that translate themselves into
Payment EOs, but I don't see a compelling reason to do that here.
Ultimately my goals are: fast entry, validation on the entry,
account information lookup etc.
Ajax might be of use here, it could be doing the account name lookup/
validation while the user was entering more data.
Chuck
--
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