Thanks Lee...I'm going to try the SQLite way...seems cleaner somehow. As to workers, I have never used them, but need to with RemoteObject calls in this same application. I want to do the RemoteObject calls in the background to avoid having the UI freeze up. Hoping I can find a good tutorial somewhere...though it is a pretty new topic.
Am I correct in thinking that handing the communication with remote data over to 'workers' will keep my interface from stalling? Mark -----Original Message----- From: Lee Burrows [mailto:[email protected]] Sent: Friday, November 08, 2013 2:03 PM To: [email protected] Subject: Re: SQLite query vs. Filtering ArrayCollection i dont think there's a simple answer - it depends on the amount of data you are dealing with, whether the database is indexed etc. i would say, the more data to deal with, the more likely that a SQL call would be quicker (and probably with a lower memory footprint). to confuse matters, a third option would be to use workers to handle the filtering in the background. On 08/11/2013 18:30, Mark Fuqua wrote: > I have a mobile application which gets its data from a SQLite database. > Query results are really fast. > > > > Right now, the application hits the database and converts the result > into an ArrayCollection. I need to allow for filtering the > ArrayCollection.seems like it might be just a quick to hit the > database again with filtering criteria rather than using the built-in > filtering function of the ArrayCollection. Is it substantially > quicker to use a filter function rather than hit the SQLite database > again and loading the result into the same ArrayCollection? > > > > Mark Fuqua > > > > [email protected] > > > > 2301 Mount Carmel Road > > Parkton, MD 21120 > > (410) 215-7356 > > > > www.availdata.com > > > > -- Lee Burrows ActionScripter
