SQLite data storage

[stephen barncard]

More complex and faster searches and joins are usually a good reason for a
'real' database, as well as the fact that a database has all the inbuilt
methods for adding, and deleting records and other management tasks. The
distinction is  more relevant when getting into bigger data sets.

However, in the flat data world, a datagrid in conjunction with arrays can
meet the needs of 90% of most database applications. Trevor Devor's
Datagrid is a one of the most amazing and useful features of LIvecode, and
makes it a snap to integrate a manipulatable database and display into an
application.

On Fri, Mar 22, 2013 at 11:45 AM, Chris Sheffield <cmsheffield at icloud.com>wrote:

> Hi Peter,
>
> For us, main reason to use a database rather than just a text file is
> simply to make the data a little more secure. I mean, it doesn't have to be
> way secure. But we do want to make it a little more difficult for someone
> with prying eyes to get hold of it. I also liked the idea of using the
> power of SQL to search and filter results for me. With a text file, to do
> it the easy way, you have to read the entire file into memory every time
> you access it. I didn't want to have to do that, being a mobile app and all.
>
> But to answer your question, yes, I could probably just use a
> tab-delimited text file and call it good. I just finished my import of the
> data and there are just over 8100 records. So nothing too huge. But like I
> said, I wanted to be able to run SQL queries on the data, and that can't be
> done with a text file, obviously.
>
> Thanks,
> Chris
>
>
> On Mar 22, 2013, at 11:43 AM, Peter Alcibiades <
> palcibiades-first at yahoo.co.uk> wrote:
>
> > Can I ask what is probably a really silly question?  Could you just use
> a tab
> > separated text file to hold this amount of data, as long as there is only
> > one table?
> >
> > I am a complete amateur of course so I probably did it all wrong.  I had
> to
> > accumulate 15,000+ records, adding to them as time went on, and
> periodically
> > go through and extract reports.  Not wishing to struggle with 'proper
> > databases' I just stuck the records into a tab delimited file, and had at
> > it.  Making backups as seemed prudent.  Nothing ever went wrong.  It ran
> > reasonably fast on a very old and obsolete spare machine.  Also the nice
> > thing was, the customer could just take a copy of the file and read it
> back
> > into Excel and do any sort of analysis or custom reports they wanted.
> >
> > Probably there is some reason for using sqlite that I'm not aware of?
> >
> > Peter
> >
> >
> >
> > --
> > View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/SQLite-data-storage-tp4662380p4662429.html
> > Sent from the Revolution - User mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 



Stephen Barncard
San Francisco Ca. USA

more about sqb  <http://www.google.com/profiles/sbarncar>