bobs at twft.com
Mon Jun 18 13:50:25 EDT 2012
Yes I did in fact, but I have decided that for purposes of searching, I want to work with a fixed data set. When a form is opened I want to load the data as it is at the time the form is opened. There will be a refresh option as well, and before I save data, I do verifications which include no time and date collisions for scheduled data, and no duplicates for unique fields.
At some point in the future I will probably want to make a mobile app for what I am doing, and efficiency in data usage, especially considering most provider's strict rules involving bandwidth usage will be paramount.
On Jun 18, 2012, at 10:38 AM, Peter Haworth wrote:
> Hi Bob,
> Have you taken into account that the data you are filtering may be out of
> date by the time it gets filtered in memory because data was either added,
> changed, or deleted in your database?
> That's an application-dependant issue of course so maybe it either doesn't
> matter or can't happen in your app.
> lcSQL Software <http://www.lcsql.com>
> On Mon, Jun 18, 2012 at 10:00 AM, Bob Sneidar <bobs at twft.com> wrote:
>> Hi Dick.
>> For simple arrays this will work well. I am envisioning large datasets,
>> and I want to filter based upon a substring being present in a list of
>> columns I provide. The goal is to create a comprehensive find field that
>> works much the way a Spotlight search works, only on SQL data.
>> Some will say, "Why not just query your SQL database over and over?" Good
>> point, but the process of requerying a database, particularly one like
>> On-Rev's from a remote location seems a little too much, but it does bring
>> up an interesting point: What if I can save an array as a memory based
>> sqLite table (it would have to be very specific in it's structure, say a 2
>> dimensional array like the one a Datagrid uses) and then I could query the
>> sql table extremely quickly.
>> This is the line I am taking at present.
More information about the Use-livecode