Hi, Niall, On Mon, Nov 21, 2016 at 12:52 PM, Niall O'Reilly <niall.orei...@ucd.ie> wrote: > On 21 Nov 2016, at 17:29, John R. Sowden wrote: > >> First of all, I come from the dBASE/Foxpro world. There is no distinction >> between a table and a database. I understand that with Sqlite a database >> includes tables and other items. The scenario that I do not understand, is: >> say I have a log file with about 7 fields totaling about 80 characters per >> record. How do I name the database and table. Currently I say log16 for >> the year 2016. > > > There's no one true way to do this. > > I've read Igor Korot's reply, and what he suggests may well be what you > need.
You are of course correct. It does depend on an application. However, I tried to explain the SQLite and its paradigm in terms of the dBase/FoxPro. Thank you. > > In a previous job, I had an application where it made sense to use a > different > database file for each time period, and always to call the table > 'LOGENTRY'. > This was because I had to deal with hundreds of thousands of records a > day, > and seldom had queries whose scope was broader than a single calendar day. > > I hope this helps a little. > > Best regards, > Niall O'Reilly > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users