RE: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread Jerry Jalenak
Blvd. Lenexa, KS 66219 (913) 577-1496 [EMAIL PROTECTED] > -Original Message- > From: Vic Cekvenich [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 06, 2003 9:32 AM > To: [EMAIL PROTECTED] > Subject: Re: [OT - Design] Needing Fast Access to 300,000 Records > > &g

Re: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread Vic Cekvenich
[EMAIL PROTECTED] wrote: retrieving all the records because just in case the client may need them does not look very efficient approach to me. One never designs for all the exceptions of what might be, that would be a bad design. One designs for the likely case only, at least good designers do. T

Re: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread Vic Cekvenich
sage- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 8:46 AM To: [EMAIL PROTECTED] Subject: Re: [OT - Design] Needing Fast Access to 300,000 Records Jerry Jalenak wrote: Hi All - I've been trying to figure out a good way of handling something, and just c

RE: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread shirishchandra.sakhare
: 'Struts Users Mailing List' Subject: RE: [OT - Design] Needing Fast Access to 300,000 Records Vic - This is still in the design stage, so I don't have a SQL statement to provide. I'm looking for the best approach to handling what is essentially a table lookup w

RE: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread Greg Hess
To avoid having 300,000 records sitting in memory I generally have my queries return record id's. My DAO returns an int[] or ResultObjects collection containing record id's that I store in some scope(session) as it takes little mem. The records are not generally all displayed at once so I only fetc

RE: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread Jerry Jalenak
Original Message- > From: Vic Cekvenich [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 06, 2003 8:46 AM > To: [EMAIL PROTECTED] > Subject: Re: [OT - Design] Needing Fast Access to 300,000 Records > > > > Jerry Jalenak wrote: > > Hi All - > > > > I

Re: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread David Graham
--- Jerry Jalenak <[EMAIL PROTECTED]> wrote: > Hi All - > > I've been trying to figure out a good way of handling something, and > just > can't quite seem to get a grip on the best approach. Here's what I've > got: > > Two database tables - Table 1 has a BILLING_CODE and an ACCOUNT_CODE. > Ta

Re: [OT - Design] Needing Fast Access to 300,000 Records

2003-11-06 Thread Vic Cekvenich
Jerry Jalenak wrote: Hi All - I've been trying to figure out a good way of handling something, and just can't quite seem to get a grip on the best approach. Here's what I've got: Two database tables - Table 1 has a BILLING_CODE and an ACCOUNT_CODE. Table 2 has the ACCOUNT_CODE and other account