![\"\"](\"https:\/\/examples.javacodegeeks.com\/wp-content\/uploads\/2022\/07\/SQLite-Tutorial-1024x576.jpg\")
<\/a>SQLite is a compact library. With all features enabled, the library size can be less than 600KiB, depending on the target platform and compiler optimization settings. There is a tradeoff between memory usage and speed. SQLite responds gracefully to memory allocation failures and disk I\/O errors. Transactions are ACID<\/a> even if interrupted by system crashes or power failures.<\/p>\n You can download the installable from this link<\/a>. You can also build the sqlite3 executable by downloading the source code from SQLite downloads<\/a>. You can use the command below extract the tar from gzipped file. You can make and make install after extracting the tar file. The output is shown below:<\/p>\n building sqlite3<\/em><\/span><\/p>\n You can run the sqlite3 using the executable and try .help command. The output is shown below. help command<\/em><\/span><\/p>\n You can try .databases command to show the databases (default) in sqlite. The output is shown below:<\/p>\n Default databases command<\/em><\/span><\/p>\n You should not compare SQLite with traditional client\/server SQL databases like MySQL, Oracle, PostgreSQL. Client\/server SQL database engines strive to implement a shared repository of enterprise data. They emphasize scalability, concurrency, centralization, and control. SQLite emphasizes economy, efficiency, reliability, independence, and simplicity.<\/p>\n SQLite database requires very little administration as compared to the traditional client\/server SQL databases. That is why it is a good fit for use in cellphones, set-top boxes, televisions, game consoles, cameras, watches, kitchen appliances, thermostats, automobiles, machine tools, airplanes, remote sensors, drones, medical devices, robots etc.<\/p>\n SQLite works best for the website which has low traffic. The amount of web traffic the SQLite can handle depends on how much the website uses its database.<\/p>\n Various tools can be used to extract data from the CSV file. This data then can be analyzed using different languages – e.g. Python, R, etc. This can also be done in a traditional SQL database but SQLite is easier to install and use and it’s just one file that we will be processing for the analysis.<\/p>\n Because an SQLite database is a single compact file in a well-defined cross-platform format, it is often used as a container for transferring content from one system to another. The sender gathers content into an SQLite database file, transfers that one file to the receiver, then the receiver uses SQL to extract the content as needed.<\/p>\n Many programs use Because of the simplicity of the SQLite database, it is a good candidate to use for education purposes. Students can create as many databases as they like and can send the DB file to the tutor for grading purposes.<\/p>\n In this section, we will discuss the cases where it is better to use the traditional client\/server databases rather than SQLite.<\/p>\n In a scenario where we have multiple clients calling the servers which require database access, it is better to use the traditional client\/server SQL database. SQLite will work but if the load becomes more the performance will reduce drastically. Another issue is that SQLite uses one file – so if multiple threads\/processes try to access this file we could see locking issues.<\/p>\n SQLite will not be the best option for websites that handle lots of transactions.<\/p>\n An SQLite database is limited in size to 281 terabytes. Even if it could handle larger databases, SQLite stores the entire database in a single disk file, and many filesystems limit the maximum size of files to something less than this. So if you think that your data size could be more than this you should consider using the traditional client\/server SQL database.<\/p>\n SQLite supports an unlimited number of simultaneous readers, but it will only allow one writer at any instant in time. So if you are building an application that requires lots of writes in a quick interval of time then it is better to use the traditional client\/server SQL database.<\/p>\n In this section, we will see the difference between SQLite and a traditional client\/server database – e.g. MySQL.<\/p>\n A traditional client\/server database requires some setup and configuration before you can start using it. SQLite doesn’t need to be installed before it can be used. There is no set-up process for it. You don’t need to start\/stop the server as you do in the case of a traditional database. SQLite uses no configuration files. Nothing needs to be done to tell the system that SQLite is running. No actions are required to recover after a system crash or power failure. There is nothing to troubleshoot.<\/p>\n Most SQL database engines are implemented as a separate server process. Programs that want to access the database communicate with the server using some kind of interprocess communication (typically TCP\/IP) to send requests to the server and to receive back results. SQLite does not work this way. With SQLite, the process that wants to access the database reads and writes directly from the database files on disk. There is no intermediary server process.<\/p>\n There are advantages and disadvantages to being serverless. The main advantage is that there is no separate server process to install, set up, configure, initialize, manage, and troubleshoot. This is one reason why SQLite is a “zero-configuration” database engine. Programs that use SQLite require no administrative support for setting up the database engine before they are run. Any program that is able to access the disk is able to use an SQLite database.<\/p>\n On the other hand, a database engine that uses a server can provide better protection from bugs in the client application – stray pointers in a client cannot corrupt memory on the server. And because a server is a single persistent process, it is able to control database access with more precision, allowing for finer grain locking and better concurrency.<\/p>\n An SQLite database is a single ordinary disk file that can be located anywhere in the directory hierarchy. If SQLite can read the disk file then it can read anything in the database. If the disk file and its directory are writable, then SQLite can change anything in the database. Database files can easily be copied onto a USB memory stick or emailed for sharing.<\/p>\n Other SQL database engines tend to store data as a large collection of files. Often these files are in a standard location that only the database engine itself can access. This makes the data more secure, but also makes it harder to access. Some SQL database engines provide the option of writing directly to disk and bypassing the filesystem altogether. This provides added performance, but at the cost of considerable setup and maintenance complexity.<\/p>\n In this section, we will see how SQLite language differs from the traditional client\/server databases.<\/p>\n SQLite is very flexible with regard to data types. SQLite is very forgiving of the type of data that you put into the database. For example, if a column has a datatype of Unlike most other SQL implementations, SQLite does not have a separate SQLite has no Because SQLite is flexible and forgiving with regard to data types, table columns can be created that have no specified datatype at all<\/p>\n In this article, we discussed the SQLite database. We discussed its use and how it is different from traditional client\/server SQL databases. We looked at the scenarios where it will be good to use SQLite and also those where it will not perform better. In the end, we looked at some of the language differences.<\/p>\n Last updated on Apr. 5th, 2022<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" 1. Introduction SQLite is an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. It is free and you don’t need to buy any license to use it. It is one of the most commonly used DB. Unlike most SQL databases, it does not have a separate server process. It reads and …<\/p>\n","protected":false},"author":34,"featured_media":1204,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[53],"tags":[1728],"class_list":["post-104568","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sql","tag-sqlite"],"yoast_head":"\n2. SQLite Installation<\/h2>\n
apples-MacBook-Air:downloads bhagvan.kommadi$ cd sqlite-autoconf-3380200\napples-MacBook-Air:sqlite-autoconf-3380200 bhagvan.kommadi$ ls\nINSTALL\t\t\tconfig.guess\t\tsqlite3.1\nMakefile.am\t\tconfig.sub\t\tsqlite3.c\nMakefile.fallback\tconfigure\t\tsqlite3.h\nMakefile.in\t\tconfigure.ac\t\tsqlite3.pc.in\nMakefile.msc\t\tdepcomp\t\t\tsqlite3.rc\nREADME.txt\t\tinstall-sh\t\tsqlite3ext.h\nReplace.cs\t\tltmain.sh\t\tsqlite3rc.h\naclocal.m4\t\tmissing\t\t\ttea\ncompile\t\t\tshell.c\napples-MacBook-Air:sqlite-autoconf-3380200 bhagvan.kommadi$ .\/configure --prefix=\/usr\/local\nchecking for a BSD-compatible install... \/usr\/local\/bin\/ginstall -c\nchecking whether build environment is sane... yes\nchecking for a thread-safe mkdir -p... \/usr\/local\/bin\/gmkdir -p\nchecking for gawk... no\nchecking for mawk... no\nchecking for nawk... no\nchecking for awk... awk\nchecking whether make sets $(MAKE)... make\nyes\nchecking whether make supports nested variables... yes\nchecking for style of include used by make... GNU\nchecking for gcc... gcc\nchecking whether the C compiler works... yes\nchecking for C compiler default output file name... a.out\nchecking for suffix of executables... \nchecking whether we are cross compiling... no\nchecking for suffix of object files... o\nchecking whether we are using the GNU C compiler... yes\nchecking whether gcc accepts -g... yes\nchecking for gcc option to accept ISO C89... none needed\nchecking whether gcc understands -c and -o together... yes\nchecking dependency style of gcc... gcc3\nchecking for special C compiler options needed for large files... no\nchecking for _FILE_OFFSET_BITS value needed for large files... no\nchecking for gcc... (cached) gcc\nchecking whether we are using the GNU C compiler... (cached) yes\nchecking whether gcc accepts -g... (cached) yes\nchecking for gcc option to accept ISO C89... (cached) none needed\nchecking whether gcc understands -c and -o together... (cached) yes\nchecking dependency style of gcc... (cached) gcc3\nchecking build system type... x86_64-apple-darwin20.6.0\nchecking host system type... x86_64-apple-darwin20.6.0\nchecking how to print strings... printf\nchecking for a sed that does not truncate output... \/usr\/bin\/sed\nchecking for grep that handles long lines and -e... \/usr\/bin\/grep\nchecking for egrep... \/usr\/bin\/grep -E\nchecking for fgrep... \/usr\/bin\/grep -F\nchecking for ld used by gcc... \/Applications\/Xcode.app\/Contents\/Developer\/Toolchains\/XcodeDefault.xctoolchain\/usr\/bin\/ld\nchecking if the linker (\/Applications\/Xcode.app\/Contents\/Developer\/Toolchains\/XcodeDefault.xctoolchain\/usr\/bin\/ld) is GNU ld... no\nchecking for BSD- or MS-compatible name lister (nm)... \/usr\/bin\/nm -B\nchecking the name lister (\/usr\/bin\/nm -B) interface... BSD nm\nchecking whether ln -s works... yes\nchecking the maximum length of command line arguments... 786432\nchecking how to convert x86_64-apple-darwin20.6.0 file names to x86_64-apple-darwin20.6.0 format... func_convert_file_noop\nchecking how to convert x86_64-apple-darwin20.6.0 file names to toolchain format... func_convert_file_noop\nchecking for \/Applications\/Xcode.app\/Contents\/Developer\/Toolchains\/XcodeDefault.xctoolchain\/usr\/bin\/ld option to reload object files... -r\nchecking for objdump... objdump\nchecking how to recognize dependent libraries... pass_all\nchecking for dlltool... no\nchecking how to associate runtime and link libraries... printf %s\\n\nchecking for ar... ar\nchecking for archiver @FILE support... no\nchecking for strip... strip\nchecking for ranlib... ranlib\nchecking command to parse \/usr\/bin\/nm -B output from gcc object... ok\nchecking for sysroot... no\nchecking for a working dd... \/bin\/dd\nchecking how to truncate binary pipes... \/bin\/dd bs=4096 count=1\nchecking for mt... no\nchecking if : is a manifest tool... no\nchecking for dsymutil... dsymutil\nchecking for nmedit... nmedit\nchecking for lipo... lipo\nchecking for otool... otool\nchecking for otool64... no\nchecking for -single_module linker flag... yes\nchecking for -exported_symbols_list linker flag... yes\nchecking for -force_load linker flag... yes\nchecking how to run the C preprocessor... gcc -E\nchecking for ANSI C header files... yes\nchecking for sys\/types.h... yes\nchecking for sys\/stat.h... yes\nchecking for stdlib.h... yes\nchecking for string.h... yes\nchecking for memory.h... yes\nchecking for strings.h... yes\nchecking for inttypes.h... yes\nchecking for stdint.h... yes\nchecking for unistd.h... yes\nchecking for dlfcn.h... yes\nchecking for objdir... .libs\nchecking if gcc supports -fno-rtti -fno-exceptions... yes\nchecking for gcc option to produce PIC... -fno-common -DPIC\nchecking if gcc PIC flag -fno-common -DPIC works... yes\nchecking if gcc static flag -static works... no\nchecking if gcc supports -c -o file.o... yes\nchecking if gcc supports -c -o file.o... (cached) yes\nchecking whether the gcc linker (\/Applications\/Xcode.app\/Contents\/Developer\/Toolchains\/XcodeDefault.xctoolchain\/usr\/bin\/ld) supports shared libraries... yes\nchecking dynamic linker characteristics... darwin20.6.0 dyld\nchecking how to hardcode library paths into programs... immediate\nchecking whether stripping libraries is possible... yes\nchecking if libtool supports shared libraries... yes\nchecking whether to build shared libraries... yes\nchecking whether to build static libraries... yes\nchecking for fdatasync... yes\nchecking for usleep... yes\nchecking for fullfsync... no\nchecking for localtime_r... yes\nchecking for gmtime_r... yes\nchecking whether strerror_r is declared... yes\nchecking for strerror_r... yes\nchecking whether strerror_r returns char *... no\nchecking editline\/readline.h usability... yes\nchecking editline\/readline.h presence... yes\nchecking for editline\/readline.h... yes\nchecking for library containing readline... no\nchecking readline\/readline.h usability... yes\nchecking readline\/readline.h presence... yes\nchecking for readline\/readline.h... yes\nchecking for library containing tgetent... -ltermcap\nchecking for library containing readline... -lreadline\nchecking for library containing pthread_create... none required\nchecking for library containing pthread_mutexattr_init... none required\nchecking for library containing dlopen... none required\nchecking for whether to support dynamic extensions... yes\nchecking SQL math functions... enabled\nchecking for library containing ceil... none required\nchecking FTS4 extension... enabled\nchecking FTS3 extension... disabled\nchecking FTS5 extension... enabled\nchecking for library containing log... none required\nchecking RTREE extension... enabled\nchecking Session extension... disabled\nchecking Build type... release\nchecking for posix_fallocate... no\nchecking zlib.h usability... yes\nchecking zlib.h presence... yes\nchecking for zlib.h... yes\nchecking for library containing deflate... -lz\nchecking for library containing system... none required\nchecking that generated files are newer than configure... done\nconfigure: creating .\/config.status\nconfig.status: creating Makefile\nconfig.status: creating sqlite3.pc\nconfig.status: executing depfiles commands\nconfig.status: executing libtool commands\napples-MacBook-Air:sqlite-autoconf-3380200 bhagvan.kommadi$ make\n\/bin\/sh .\/libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\\\"sqlite\\\" -DPACKAGE_TARNAME=\\\"sqlite\\\" -DPACKAGE_VERSION=\\\"3.38.2\\\" -DPACKAGE_STRING=\\\"sqlite\\ 3.38.2\\\" -DPACKAGE_BUGREPORT=\\\"http:\/\/www.sqlite.org\\\" -DPACKAGE_URL=\\\"\\\" -DPACKAGE=\\\"sqlite\\\" -DVERSION=\\\"3.38.2\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs\/\\\" -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_DECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 -DHAVE_READLINE_READLINE_H=1 -DHAVE_READLINE=1 -DHAVE_ZLIB_H=1 -I. -I\/usr\/local\/opt\/krb5\/include -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -g -O2 -MT sqlite3.lo -MD -MP -MF .deps\/sqlite3.Tpo -c -o sqlite3.lo sqlite3.c\nlibtool: compile: gcc -DPACKAGE_NAME=\\\"sqlite\\\" -DPACKAGE_TARNAME=\\\"sqlite\\\" -DPACKAGE_VERSION=\\\"3.38.2\\\" \"-DPACKAGE_STRING=\\\"sqlite 3.38.2\\\"\" -DPACKAGE_BUGREPORT=\\\"http:\/\/www.sqlite.org\\\" -DPACKAGE_URL=\\\"\\\" -DPACKAGE=\\\"sqlite\\\" -DVERSION=\\\"3.38.2\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs\/\\\" -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_DECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 -DHAVE_READLINE_READLINE_H=1 -DHAVE_READLINE=1 -DHAVE_ZLIB_H=1 -I. -I\/usr\/local\/opt\/krb5\/include -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -g -O2 -MT sqlite3.lo -MD -MP -MF .deps\/sqlite3.Tpo -c sqlite3.c -fno-common -DPIC -o .libs\/sqlite3.o\nlibtool: compile: gcc -DPACKAGE_NAME=\\\"sqlite\\\" -DPACKAGE_TARNAME=\\\"sqlite\\\" -DPACKAGE_VERSION=\\\"3.38.2\\\" \"-DPACKAGE_STRING=\\\"sqlite 3.38.2\\\"\" -DPACKAGE_BUGREPORT=\\\"http:\/\/www.sqlite.org\\\" -DPACKAGE_URL=\\\"\\\" -DPACKAGE=\\\"sqlite\\\" -DVERSION=\\\"3.38.2\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs\/\\\" -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_DECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 -DHAVE_READLINE_READLINE_H=1 -DHAVE_READLINE=1 -DHAVE_ZLIB_H=1 -I. -I\/usr\/local\/opt\/krb5\/include -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -g -O2 -MT sqlite3.lo -MD -MP -MF .deps\/sqlite3.Tpo -c sqlite3.c -o sqlite3.o >\/dev\/null 2>&1\nmv -f .deps\/sqlite3.Tpo .deps\/sqlite3.Plo\n\/bin\/sh .\/libtool --tag=CC --mode=link gcc -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -g -O2 -no-undefined -version-info 8:6:8 -L\/usr\/local\/opt\/krb5\/lib -o libsqlite3.la -rpath \/usr\/local\/lib sqlite3.lo -lz \nlibtool: link: gcc -dynamiclib -o .libs\/libsqlite3.0.dylib .libs\/sqlite3.o -L\/usr\/local\/opt\/krb5\/lib -lz -g -O2 -install_name \/usr\/local\/lib\/libsqlite3.0.dylib -compatibility_version 9 -current_version 9.6 -Wl,-single_module\nlibtool: link: (cd \".libs\" && rm -f \"libsqlite3.dylib\" && ln -s \"libsqlite3.0.dylib\" \"libsqlite3.dylib\")\nlibtool: link: ar cru .libs\/libsqlite3.a sqlite3.o\nlibtool: link: ranlib .libs\/libsqlite3.a\nlibtool: link: ( cd \".libs\" && rm -f \"libsqlite3.la\" && ln -s \"..\/libsqlite3.la\" \"libsqlite3.la\" )\ngcc -DPACKAGE_NAME=\\\"sqlite\\\" -DPACKAGE_TARNAME=\\\"sqlite\\\" -DPACKAGE_VERSION=\\\"3.38.2\\\" -DPACKAGE_STRING=\\\"sqlite\\ 3.38.2\\\" -DPACKAGE_BUGREPORT=\\\"http:\/\/www.sqlite.org\\\" -DPACKAGE_URL=\\\"\\\" -DPACKAGE=\\\"sqlite\\\" -DVERSION=\\\"3.38.2\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs\/\\\" -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_DECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 -DHAVE_READLINE_READLINE_H=1 -DHAVE_READLINE=1 -DHAVE_ZLIB_H=1 -I. -I\/usr\/local\/opt\/krb5\/include -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBSTAT_VTAB -g -O2 -MT sqlite3-shell.o -MD -MP -MF .deps\/sqlite3-shell.Tpo -c -o sqlite3-shell.o `test -f 'shell.c' || echo '.\/'`shell.c\nmv -f .deps\/sqlite3-shell.Tpo .deps\/sqlite3-shell.Po\ngcc -DPACKAGE_NAME=\\\"sqlite\\\" -DPACKAGE_TARNAME=\\\"sqlite\\\" -DPACKAGE_VERSION=\\\"3.38.2\\\" -DPACKAGE_STRING=\\\"sqlite\\ 3.38.2\\\" -DPACKAGE_BUGREPORT=\\\"http:\/\/www.sqlite.org\\\" -DPACKAGE_URL=\\\"\\\" -DPACKAGE=\\\"sqlite\\\" -DVERSION=\\\"3.38.2\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs\/\\\" -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_DECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 -DHAVE_READLINE_READLINE_H=1 -DHAVE_READLINE=1 -DHAVE_ZLIB_H=1 -I. -I\/usr\/local\/opt\/krb5\/include -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBSTAT_VTAB -g -O2 -MT sqlite3-sqlite3.o -MD -MP -MF .deps\/sqlite3-sqlite3.Tpo -c -o sqlite3-sqlite3.o `test -f 'sqlite3.c' || echo '.\/'`sqlite3.c\nmv -f .deps\/sqlite3-sqlite3.Tpo .deps\/sqlite3-sqlite3.Po\n\/bin\/sh .\/libtool --tag=CC --mode=link gcc -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBSTAT_VTAB -g -O2 -L\/usr\/local\/opt\/krb5\/lib -o sqlite3 sqlite3-shell.o sqlite3-sqlite3.o -lreadline -ltermcap -lz \nlibtool: link: gcc -D_REENTRANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_GEOPOLY -DSQLITE_HAVE_ZLIB -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBSTAT_VTAB -g -O2 -o sqlite3 sqlite3-shell.o sqlite3-sqlite3.o -L\/usr\/local\/opt\/krb5\/lib -lreadline -ltermcap -lz\napples-MacBook-Air:sqlite-autoconf-3380200 bhagvan.kommadi$ make install\n \/usr\/local\/bin\/gmkdir -p '\/usr\/local\/lib'\n \/bin\/sh .\/libtool --mode=install \/usr\/local\/bin\/ginstall -c libsqlite3.la '\/usr\/local\/lib'\nlibtool: install: \/usr\/local\/bin\/ginstall -c .libs\/libsqlite3.0.dylib \/usr\/local\/lib\/libsqlite3.0.dylib\nlibtool: install: (cd \/usr\/local\/lib && { ln -s -f libsqlite3.0.dylib libsqlite3.dylib || { rm -f libsqlite3.dylib && ln -s libsqlite3.0.dylib libsqlite3.dylib; }; })\nlibtool: install: \/usr\/local\/bin\/ginstall -c .libs\/libsqlite3.lai \/usr\/local\/lib\/libsqlite3.la\nlibtool: install: \/usr\/local\/bin\/ginstall -c .libs\/libsqlite3.a \/usr\/local\/lib\/libsqlite3.a\nlibtool: install: chmod 644 \/usr\/local\/lib\/libsqlite3.a\nlibtool: install: ranlib \/usr\/local\/lib\/libsqlite3.a\n \/usr\/local\/bin\/gmkdir -p '\/usr\/local\/bin'\n \/bin\/sh .\/libtool --mode=install \/usr\/local\/bin\/ginstall -c sqlite3 '\/usr\/local\/bin'\nlibtool: install: \/usr\/local\/bin\/ginstall -c sqlite3 \/usr\/local\/bin\/sqlite3\n \/usr\/local\/bin\/gmkdir -p '\/usr\/local\/include'\n \/usr\/local\/bin\/ginstall -c -m 644 sqlite3.h sqlite3ext.h '\/usr\/local\/include'\n \/usr\/local\/bin\/gmkdir -p '\/usr\/local\/share\/man\/man1'\n \/usr\/local\/bin\/ginstall -c -m 644 sqlite3.1 '\/usr\/local\/share\/man\/man1'\n \/usr\/local\/bin\/gmkdir -p '\/usr\/local\/lib\/pkgconfig'\n \/usr\/local\/bin\/ginstall -c -m 644 sqlite3.pc '\/usr\/local\/lib\/pkgconfig'\n<\/pre>\napples-MacBook-Air:sqlite-autoconf-3380200 bhagvan.kommadi$ .\/sqlite3\nSQLite version 3.38.2 2022-03-26 13:51:10\nEnter \".help\" for usage hints.\nConnected to a transient in-memory database.\nUse \".open FILENAME\" to reopen on a persistent database.\nsqlite> .help\n.archive ... Manage SQL archives\n.auth ON|OFF Show authorizer callbacks\n.backup ?DB? FILE Backup DB (default \"main\") to FILE\n.bail on|off Stop after hitting an error. Default OFF\n.binary on|off Turn binary output on or off. Default OFF\n.cd DIRECTORY Change the working directory to DIRECTORY\n.changes on|off Show number of rows changed by SQL\n.check GLOB Fail if output since .testcase does not match\n.clone NEWDB Clone data into NEWDB from the existing database\n.connection [close] [#] Open or close an auxiliary database connection\n.databases List names and files of attached databases\n.dbconfig ?op? ?val? List or change sqlite3_db_config() options\n.dbinfo ?DB? Show status information about the database\n.dump ?OBJECTS? Render database content as SQL\n.echo on|off Turn command echo on or off\n.eqp on|off|full|... Enable or disable automatic EXPLAIN QUERY PLAN\n.excel Display the output of next command in spreadsheet\n.exit ?CODE? Exit this program with return-code CODE\n.expert EXPERIMENTAL. Suggest indexes for queries\n.explain ?on|off|auto? Change the EXPLAIN formatting mode. Default: auto\n.filectrl CMD ... Run various sqlite3_file_control() operations\n.fullschema ?--indent? Show schema and the content of sqlite_stat tables\n.headers on|off Turn display of headers on or off\n.help ?-all? ?PATTERN? Show help text for PATTERN\n.import FILE TABLE Import data from FILE into TABLE\n.imposter INDEX TABLE Create imposter table TABLE on index INDEX\n.indexes ?TABLE? Show names of indexes\n.limit ?LIMIT? ?VAL? Display or change the value of an SQLITE_LIMIT\n.lint OPTIONS Report potential schema issues.\n.load FILE ?ENTRY? Load an extension library\n.log FILE|off Turn logging on or off. FILE can be stderr\/stdout\n.mode MODE ?OPTIONS? Set output mode\n.nonce STRING Suspend safe mode for one command if nonce matches\n.nullvalue STRING Use STRING in place of NULL values\n.once ?OPTIONS? ?FILE? Output for the next SQL command only to FILE\n.open ?OPTIONS? ?FILE? Close existing database and reopen FILE\n.output ?FILE? Send output to FILE or stdout if FILE is omitted\n.parameter CMD ... Manage SQL parameter bindings\n.print STRING... Print literal STRING\n.progress N Invoke progress handler after every N opcodes\n.prompt MAIN CONTINUE Replace the standard prompts\n.quit Exit this program\n.read FILE Read input from FILE or command output\n.recover Recover as much data as possible from corrupt db.\n.restore ?DB? FILE Restore content of DB (default \"main\") from FILE\n.save ?OPTIONS? FILE Write database to FILE (an alias for .backup ...)\n.scanstats on|off Turn sqlite3_stmt_scanstatus() metrics on or off\n.schema ?PATTERN? Show the CREATE statements matching PATTERN\n.selftest ?OPTIONS? Run tests defined in the SELFTEST table\n.separator COL ?ROW? Change the column and row separators\n.sha3sum ... Compute a SHA3 hash of database content\n.shell CMD ARGS... Run CMD ARGS... in a system shell\n.show Show the current values for various settings\n.stats ?ARG? Show stats or turn stats on or off\n.system CMD ARGS... Run CMD ARGS... in a system shell\n.tables ?TABLE? List names of tables matching LIKE pattern TABLE\n.testcase NAME Begin redirecting output to 'testcase-out.txt'\n.testctrl CMD ... Run various sqlite3_test_control() operations\n.timeout MS Try opening locked tables for MS milliseconds\n.timer on|off Turn SQL timer on or off\n.trace ?OPTIONS? Output each SQL statement as it is run\n.vfsinfo ?AUX? Information about the top-level VFS\n.vfslist List all available VFSes\n.vfsname ?AUX? Print the name of the VFS stack\n.width NUM1 NUM2 ... Set minimum column widths for columnar output\nsqlite>\n<\/pre>\n
sqlite> .databases\nmain: \"\" r\/w\nsqlite> .schema sqlite_master\nCREATE TABLE sqlite_master (\n type text,\n name text,\n tbl_name text,\n rootpage integer,\n sql text\n);\nsqlite>\n<\/pre>\n
3. Uses of SQLite<\/h2>\n
3.1 Embedded devices and IOT<\/h3>\n
3.2 Websites<\/h3>\n
3.3 Data analysis<\/h3>\n
3.4 Data transfer<\/h3>\n
3.5 Replacement for ad hoc disk files<\/h3>\n
fopen()<\/code>, fread()<\/code>, and fwrite()<\/code> to create and manage files of data in home-grown formats. SQLite works particularly well as a replacement for these ad hoc data files. Contrary to intuition, SQLite can be faster than the filesystem for reading and writing content to disk.<\/p>\n3.6 Education <\/h3>\n
4. Traditional SQL databases<\/h2>\n
4.1 Client server application<\/h3>\n
4.2 High volume websites<\/h3>\n
4.3 Lage datasets<\/h3>\n
4.4 High concurrency<\/h3>\n
5. SQLite vs traditional client\/server database<\/h2>\n
5.1 Configuration<\/h3>\n
5.2 Client\/Server<\/h3>\n
5.3 Database file<\/h3>\n
6. Language<\/h2>\n
6.1. Flexibility<\/h3>\n
INTEGER<\/code> and the application inserts a text string into that column, SQLite will first try to convert the text string into an integer, just like every other SQL database engine. Thus, if one inserts ‘1234’ into an INTEGER<\/code> column, that value is converted into an integer 1234 and stored. But, if you insert a non-numeric string like ‘wxyz’ into an INTEGER<\/code> column, unlike other SQL databases, SQLite does not throw an error. Instead, SQLite stores the actual string value in the column.<\/p>\n6.2 Booleans<\/h3>\n
BOOLEAN<\/code> datatype. Instead, TRUE<\/code> and FALSE<\/code> are (normally) represented as integers 1 and 0, respectively.<\/p>\n6.3 DATETIME<\/h3>\n
DATETIME<\/code> datatype. Instead, dates and times can be stored in any of these ways:<\/p>\n\n
TEXT<\/code> string in the ISO-8601 format. Example: ‘2018-04-02 12:13:46<\/em>‘.<\/li>\nINTEGER<\/code> number of seconds since 1970 (also known as “unix time”).<\/li>\nREAL<\/code> value that is the fractional Julian day number.<\/li>\n<\/ul>\n6.4 Datatype is optional<\/h3>\n
7. Summary<\/h2>\n