John,

There is a lot of documentation on the SQLite website.

Here's the 'official' docs on creating a table https://www.sqlite.org/lang_createtable.html

A Sqlite database consists of many tables. I am unsure if there is an upper limit, if there is, its more tables than I have ever created. You probably need to read up a bit more on SQL in general and SQLite in particular. Its a great SQL database for many uses, though not for every use. Here's a summary https://sqlite.org/whentouse.

SQLite does not set limits on text fields. Thats a great strength (some people may disagree), see here https://www.sqlite.org/datatype3.html

You can create a table and specify the text length but its there for compatibility and is ignored. You want to drop 20, 200 or 2000 chars in your field, go ahead and do it.

SQLite is very flexible and very fast, there's a ton of help and docs out there, the support is direct from the people who write it.

Rob


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.

Secondly, I have 2 "front ends" for Sqlite on my Ubuntu 16.04 computer. Neither one allows me to set the length of the text fields in the table creation process. How does the Sqlite know how long each record should be, same with integers.

No help found in the documentation on the Sqlite web site.

John

_______________________________________________
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

Reply via email to