How to download & install sqlite on windows

Source install

To skip searching for pre-compiled binaries, and force a build from source, use

The sqlite3 module depends only on libsqlite3. However, by default, an internal/bundled copy of sqlite will be built and statically linked, so an externally installed sqlite3 is not required.

If you wish to install against an external sqlite then you need to pass the argument to wrapper:

If building against an external sqlite3 make sure to have the development headers available. Mac OS X ships with these by default. If you don’t have them installed, install the package with your package manager, e.g. for Debian/Ubuntu. Make sure that you have at least >= 3.6.

Note, if building against homebrew-installed sqlite on OS X you can do:

By default the node-gyp install will use as part of the installation. A
different python executable can be specified on the command line.

This uses the npm_config_python config, so values in .npmrc will be honoured:

Bug fixes

  • Fix loading of project files with empty filter values (#2288)
  • Fix initial table view when using the -t / –table command line option (#2113)
  • Add status message when opening a file from the recent file list (4dfe4f76db3667e67c112cfdd5e37a2f7f8bc6d1)
  • Make sure to not show “NULL” for empty but non-NULL values in the Edit dialog (#2204)
  • Fix plot being drawn before all data is loaded (#2286)
  • Restore original default for having condition format in filter line (f28ecc0133a2859e750fac01fccc685e2eea7508)
  • Fix default font in the format toolbar (c4b2ffceb32c9c826268702c14b5f3c67c55c45e)
  • Improve binary detection for cases starting by chance by a BOM (#2197)
  • Make sure the order of the statements in the SQL log is correct (05db9014c2b7541dd21a151aa0512e5f20f47ce1)
  • Fix executing selected SQL text when there are multi-byte characters (#2311)
  • Fix executing SQL queries with compound operators (#2316)
  • Fix SQL import of files with BOM (#2323)
  • Also update schema when clicking the Refresh button in Browse Data tab (16c3d8d13ee997d0ce15737110826c484f8c8879)
  • Select column in table results when column header is pressed (#2343)
  • Tweak the output wording for command line options (#1069)
  • Remove the default property of the cancel button in the “Fetching data…” dialog (#2383)
  • Fix not being saved and not applied when modifying database cells in Windows external program (f2d8f79752f4a20b749c03f3313d9555484a0d71)
  • Fix incorrect display of SQL calltips containing non-US-ASCII characters (9f7851b4d6f31c21a98acf2a01872de654d960af)
  • Fix to ‘Window Layout’ options work properly (#2435)

Building and packaging

  • Fix CMake warning during compilation (115aa00ac5f79a6d24618daa06e5402ff1a6adbb)
  • snap: Add environment variables to set Qt theme (7b5d65220557f73f2ce36ceee80f1e5ba65160c6)
  • Updated to OpenSSL 1.1.1h for the Windows and macOS builds

Platform specific

  • No longer force Light theme on macOS when “Follow the desktop style” is chosen (508118ffd072e8f5507e4d6beaa52be8d51d4deb)
  • Keep registry key consistent on Windows (#2328)
  • Allow use of integrated graphics card instead of high performance graphics card in macOS (#2377)
  • Use native path separators in Preferences dialog (f38b829f5695bb95fbb50cb203376e3013bf2001)
  • Added message box for informative command line arguments for Windows (#1069)


  • Remove all translations of key shortcuts (0070a158617898ba4602ae04c451cec35df640fb)
  • Update of the Korean translation (#2329, 82accb2720fa06b6e2ba330338fa362c39305a3e)
  • Update of the Spanish translation (551a420791dcfa78dd14a954f7dbea00dd5eef0e)
  • Update of the Japanese translation (#2407)
  • Update of the French translation (2803da38b1e36fed59e8e56c13c201f445bda516)
  • Update of the Arabic translation (1dfa70c209453ab3fdce7991377fdba94bafccff)
  • Fixes in the Spanish translation (4791b99afff1691f2770f31e33f8ac7ca5778898, 5d85ca1a5388228af0ca092b0f51397743b46563, 454fd4a50b210c9e434bb57b54b2e4e9bf3ddd3b)
  • Fixes in the French translation (90d33c6299a447ee455013adce3af79f99b22a68, 03752066ac7675ca2ca2b350935b0944e0e7247f)
  • Update of the German translation (#2415)
  • Update of the Italian translation (#2419)
  • Update of the Portuguese translation (#2418)
  • Update of the Chinese translation (#2421)
  • Add of the Dutch translation (#2424)

Version Control

If you are reading this on GitHub or some other Git repository or service,
then you are looking at a mirror. The names of check-ins and
other artifacts in a Git mirror are different from the official
names for those objects. The offical names for check-ins are
found in a footer on the check-in comment for authorized mirrors.
The official check-in name can also be seen in the file
in the root of the tree. Always use the official name, not the
Git-name, when communicating about an SQLite check-in.

If you pulled your SQLite source code from a secondary source and want to
verify its integrity, there are hints on how to do that in the
section below.

Packaging and Building

  • Antlr is removed as a dependency
  • Niels Lohmann’s JSON library is added as a dependency. A copy of the library is included in the source code.
  • Update bundled QScintilla library to version 2.11.1 (e392e64)
  • Update bundled QHexEdit2 library to version 0.8.6 (d4401f9)
  • Update bunbled QCustomPlot library to version 2.0.1 ()
  • Update bundled QDarkStyleSheet to version 2.8 (3b2dec4)
  • More flexibility to override library paths (9f28851, b4af221, 800a8da, a692c06, )
  • Add support for building with cmake 3.11 and later ()
  • cmake installation on macOS also copies the icon and desktop files ()
  • Add workaround for Qt bugs QTBUG-68891 and QTBUG-71020 ()
  • Include a new SQLite extension for encoding and decoding base64 and decoding plist data (, )
  • Include the fileio, soundex, r-tree, and geopoly extensions (0d25d11, 5bf9015, 6565cdc)
  • Raise the maximum number of attached databases to 125 when using the bundled SQLite version (402af87, b0bca10)
  • Add MIME information file ()


  • DB.Browser.for.SQLite-3.12.0-alpha1-win32.msi
  • DB.Browser.for.SQLite-3.12.0-alpha1-win64.msi
  • DB.Browser.for.SQLite-3.12.0-alpha1.dmg


  • Version 3.12.2 released — 2021-05-18
  • Version 3.12.1 released — 2020-11-09
  • Version 3.12.0 released — 2020-06-16
  • Version 3.11.2 released — 2019-04-03
  • Version 3.11.1 released — 2019-02-18
  • Version 3.11.0 released — 2019-02-07
  • Version 3.10.1 released — 2017-09-20
  • Version 3.10.0 released — 2017-08-20
  • Version 3.9.1 released — 2016-10-03
  • Version 3.9.0 released — 2016-08-24
  • Version 3.8.0 released — 2015-12-25
  • Version 3.7.0 released — 2015-06-14
  • Version 3.6.0 released — 2015-04-27
  • Version 3.5.1 released — 2015-02-08
  • Version 3.5.0 released — 2015-01-31
  • Version 3.4.0 released — 2014-10-29
  • Version 3.3.1 released — 2014-08-31 — Project renamed from «SQLite Database Browser»
  • Version 3.3.0 released — 2014-08-24
  • Version 3.2.0 released — 2014-07-06
  • Version 3.1.0 released — 2014-05-17
  • Version 3.0.3 released — 2014-04-28
  • Version 3.0.2 released — 2014-02-12
  • Version 3.0.1 released — 2013-12-02
  • Version 3.0 released — 2013-09-15
  • Version 3.0rc1 released — 2013-09-09 — Project now on GitHub
  • Version 2.0b1 released — 2009-12-10 — Based on Qt4.6
  • Version 1.2 released — 2005-04-05
  • Version 1.1 released — 2004-07-20
  • Version 1.01 released — 2003-10-02
  • Version 1.0 released to public domain — 2003-08-19

Warranty of Title

SQLite is in the public domain and does not require a license.
Even so, some organizations want legal proof of their right to use
SQLite. Circumstances where this might occurs include the following:

  • Your company desires indemnity against claims of copyright infringement.
  • You are using SQLite in a jurisdiction that does not recognize
    the public domain.
  • You are using SQLite in a jurisdiction that does not recognize
    the right of an author to dedicate their work to the public
  • You want to hold a tangible legal document
    as evidence that you have the legal right to use and distribute
  • Your legal department tells you that you must purchase a license.

If any of the above circumstances apply to you,
Hwaci, the company that employs
all the developers of SQLite, will
sell you
a Warranty of Title for SQLite.
A Warranty of Title is a legal document that asserts that the claimed
authors of SQLite are the true authors, and that the authors
have the legal right to dedicate the SQLite to the public domain, and
that Hwaci will vigorously defend against challenges to those claims.
All proceeds from the sale of SQLite Warranties of Title are used to fund
continuing improvement and support of SQLite.

Software Licenses

The SQLite source code is in the
public domain,
and is free for use
by anyone and for any purpose. No license is required. However, some
users desire a license so that they can have warranty of title, or just
because their company lawyers say they need one. A
perpetual license
and warranty of title
for the core SQLite source code is available for this purpose.

SQLite Encryption
Extension (SEE),
the ZIPVFS Extension,
and the Compressed and
Encrypted ReadOnly Database (CEROD) extension are enhanced versions
of SQLite that handle encrypted
and/or compressed databases. SEE can read and write encrypted databases.
SEE encrypts all database content, including metadata, so that the database
file appears as white noise. ZIPVFS
compresses the database on-the-fly using application-supplied
compression and decompression functions.
CEROD reads a compressed database that is
also optionally encrypted. All of SEE, ZIPVFS, and CEROD are
supplied in source code form only; the licensee is responsible for
compiling the products for their chosen platform. It is not difficult
to compile any of these extension. All products come in the form of an
amalgamated source file
named «sqlite3.c». So compiling SEE, ZIPVFS, or CEROD into an application
is simply a matter of substituting the SEE-, ZIPVFS-, or CEROD-enabled sqlite3.c
source file in place of the public-domain sqlite3.c source file and recompiling.
Licenses for SEE, ZIPVFS, and CEROD are perpetual.
All three extension can read and write ordinary,
uncompressed and unencrypted database files.


DB Browser for SQLite works well on Linux.


Note that Debian focuses more on stability rather than newest features. Therefore packages will typically contain some older (but well tested) version, compared to the latest release.

Update the cache using:

Install the package using:

Ubuntu and Derivatives

Stable release

For Ubuntu and derivatives, @deepsidhu1313
provides a PPA with the latest release here:

To add this ppa just type in these commands in terminal:

Then update the cache using:

Install the package using:

Ubuntu 14.04.X, 15.04.X, 15.10.X and 16.04.X are supported for now (until
Launchpad decides to discontinue building for any series).

Ubuntu Precise (12.04) and Utopic (14.10) are not supported:

  • Precise does not have a new enough Qt package in its repository by default,
    which is a dependency
  • Launchpad does not support Utopic any more, which has reached its End of

Nightly builds

Nightly builds are available here:

To add this ppa, type these commands into the terminal:

Then update the cache using:

Install the package using:

On others, compile DB4S using the instructions

How It All Fits Together

Years of effort have gone into optimizating SQLite, both
for small size and high performance. And optimizations tend to result in
complex code. So there is a lot of complexity in the current SQLite
implementation. It will not be the easiest library in the world to hack.

Key files:

  • — This file defines the public interface to the SQLite
    library. Readers will need to be familiar with this interface before
    trying to understand how the library works internally.

  • sqliteInt.h — this header file defines many of the data objects
    used internally by SQLite. In addition to «sqliteInt.h», some
    subsystems have their own header files.

  • parse.y — This file describes the LALR(1) grammar that SQLite uses
    to parse SQL statements, and the actions that are taken at each step
    in the parsing process.

  • vdbe.c — This file implements the virtual machine that runs
    prepared statements. There are various helper files whose names
    begin with «vdbe». The VDBE has access to the vdbeInt.h header file
    which defines internal data objects. The rest of SQLite interacts
    with the VDBE through an interface defined by vdbe.h.

  • where.c — This file (together with its helper files named
    by «where*.c») analyzes the WHERE clause and generates
    virtual machine code to run queries efficiently. This file is
    sometimes called the «query optimizer». It has its own private
    header file, whereInt.h, that defines data objects used internally.

  • btree.c — This file contains the implementation of the B-Tree
    storage engine used by SQLite. The interface to the rest of the system
    is defined by «btree.h». The «btreeInt.h» header defines objects
    used internally by btree.c and not published to the rest of the system.

  • pager.c — This file contains the «pager» implementation, the
    module that implements transactions. The «pager.h» header file
    defines the interface between pager.c and the rest of the system.

  • os_unix.c and os_win.c — These two files implement the interface
    between SQLite and the underlying operating system using the run-time
    pluggable VFS interface.

  • — This file is not part of the core SQLite library. This
    is the file that, when linked against sqlite3.a, generates the
    «sqlite3.exe» command-line shell. The «» file is transformed
    into «shell.c» as part of the build process.

  • tclsqlite.c — This file implements the Tcl bindings for SQLite. It
    is not part of the core SQLite library. But as most of the tests in this
    repository are written in Tcl, the Tcl language bindings are important.

  • test.c* — Files in the src/ folder that begin with «test» go into
    building the «testfixture.exe» program. The testfixture.exe program is
    an enhanced Tcl shell. The testfixture.exe program runs scripts in the
    test/ folder to validate the core SQLite code. The testfixture program
    (and some other test programs too) is build and run when you type
    «make test».

  • ext/misc/json1.c — This file implements the various JSON functions
    that are build into SQLite.

There are many other source files. Each has a succinct header comment that
describes its purpose and role within the larger system.

Compiling for Unix-like systems

First create a directory in which to place
the build products. It is recommended, but not required, that the
build directory be separate from the source directory. Cd into the
build directory and then from the build directory run the configure
script found at the root of the source tree. Then run «make».

For example:

See the makefile for additional targets.

The configure script uses autoconf 2.61 and libtool. If the configure
script does not work out for you, there is a generic makefile named
«Makefile.linux-gcc» in the top directory of the source tree that you
can copy and edit to suit your needs. Comments on the generic makefile
show what changes are needed.

SQLite Studio – Manager and Administration

There are lots of SQLite management tools that make working with SQLite databases easier. Instead of creating and managing databases using a command line, these tools provide a set of GUI tools that let you create and manage the database.

The official SQLite website has dozens of such tools listed; you can view them from here: SQLite Management Tools. Here is the recommended one

SQLite Studio: It is a portable tool that doesn’t require an installation. It supports both SQLite3 and SQLite2. You can easily import and export data to various formats like CSV, HTML, PDF, JSON. Its open source and supports Unicode.

Introducing Sample database

In the following steps, we will create the sample database that we will use throughout the tutorials:

Step 1) Open a text file and paste the following commands into it:

     NVARCHAR(50)  NULL  
INSERT INTO Departments VALUES(1, 'IT');
INSERT INTO Departments VALUES(2, 'Physics');
INSERT INTO Departments VALUES(3, 'Arts');
INSERT INTO Departments VALUES(4, 'Math');

    FOREIGN KEY(DepartmentId) REFERENCES Departments(DepartmentId)
INSERT INTO Students VALUES(1, 'Michael', 1, '1998-10-12');
INSERT INTO Students VALUES(2, 'John', 1, '1998-10-12');
INSERT INTO Students VALUES(3, 'Jack', 1, '1998-10-12');
INSERT INTO Students VALUES(4, 'Sara', 2, '1998-10-12');
INSERT INTO Students VALUES(5, 'Sally', 2, '1998-10-12');
INSERT INTO Students VALUES(6, 'Jena', NULL, '1998-10-12');
INSERT INTO Students VALUES(7, 'Nancy', 2, '1998-10-12');
INSERT INTO Students VALUES(8, 'Adam', 3, '1998-10-12');
INSERT INTO Students VALUES(9, 'Stevens', 3, '1998-10-12');
INSERT INTO Students VALUES(10, 'George', NULL, '1998-10-12');

INSERT INTO  VALUES(1, 'Mid Term IT Exam', '2015-10-18');
INSERT INTO  VALUES(2, 'Mid Term Physics Exam', '2015-10-23');
INSERT INTO  VALUES(3, 'Mid Term Arts Exam', '2015-10-10');
INSERT INTO  VALUES(4, 'Mid Term Math Exam', '2015-10-15');

    FOREIGN KEY(StudentId) REFERENCES Students(StudentId),

INSERT INTO Marks VALUES(1, 1, 1, 18);
INSERT INTO Marks VALUES(2, 1, 2, 20);
INSERT INTO Marks VALUES(3, 1, 3, 16);
INSERT INTO Marks VALUES(4, 2, 4, 19);
INSERT INTO Marks VALUES(5, 2, 5, 14);
INSERT INTO Marks VALUES(6, 2, 7, 20);
INSERT INTO Marks VALUES(7, 3, 8, 20);
INSERT INTO Marks VALUES(8, 3, 9, 20);

Step 2) Save the file as “TutorialsSampleDB.sql” in the following directory “C:\sqlite“.

Step 3) Open the Windows Command Line tool (cmd.exe) from the start menu, type “cmd” and open it.

Step 4) It will open in the default path, you need to navigate to the “C:\sqlite” folder we had created earlier in this tutorial by the following command “cd “C:\sqlite”:

Step 5) Write the following command,

sqlite3 TutorialsSampleDB.db < TutorialsSampleDB.sql

The command should be completed successfully, and you should see no output after that command as the following screenshot:

Step 6) You should now be able to see the database file “TutorialsSampleDB.db” created in the directory “C:\sqlite“:

Building for node-webkit

Because of ABI differences, must be built in a custom to be used with node-webkit.

To build node-sqlite3 for node-webkit:

  1. Install globally: (unless already installed)

  2. Build the module with the custom flags of , , and :

NODE_WEBKIT_VERSION="0.8.6" # see latest version at
npm install sqlite3 --build-from-source --runtime=node-webkit --target_arch=ia32 --target=$(NODE_WEBKIT_VERSION)

This command internally calls out to which itself calls out to when the option is passed.

You can also run this command from within a checkout:

npm install --build-from-source --runtime=node-webkit --target_arch=ia32 --target=$(NODE_WEBKIT_VERSION)

Remember the following:

  • You must provide the right flag. is needed to target 32bit node-webkit builds, while will target 64bit node-webkit builds (if available for your platform).

  • After the package is built for node-webkit it cannot run in the vanilla Node.js (and vice versa).

    For example, npm test of the node-webkit’s package would fail.

Visit the “Using Node modules” article in the node-webkit’s wiki for more details.

SQLite3 manager LITE

Сайт производителя:

Цена: .

Критерий Оценка (от 0 до 2)
Функциональность 2
Цена 2
Работа с UTF-8
Русский интерфейс
Удобство 1
Итог 5

По сравнению с предыдущей программой “SQLite3 manager LITE” выглядит более функциональным. Кроме того, что можно просто просматривать данные в таблицах, также можно просматривать и создавать триггеры, индексы, представления и т.д. Дополнительно можно экспортировать все мета-данные базы данных. При этом можно создавать файлы с данными для экспорта таблиц в Paradox и Interbase.

Также в программе была предпринята попытка зделать, что-то вроде визуального мастера создания запросов наподобие MS Access, но, на мой взгляд, попытка успехом не увенчалась.

У бесплатной версии есть один недостаток – не понимает данные в кодировке UTF-8. Есть, конечно, возможность указать кодировку базы данных при открытии файла, но в списке кодировок UTF-8 отсутствует. Как работает Full-версия программы я так и не увидел, т.к. на сайте производителя чёрт ногу сломит. Висит какой-то непонятный javascript, выводящий непонятную инфу. В общем, сложилось впечатление, что проект успешно заглох.

Licenses (details below)

5. SQLite License.
Warranty of title and perpetual right-to-use for the SQLite source code.
$6000 one time fee More InfoPurchase
6. SQLite Encryption Extension (SEE).
A drop-in replacement for public-domain SQLite source code that has
the added ability to read/write AES-encrypted databases.
$2000 one time fee More InfoPurchase
7. Compressed And Encrypted Read-Only Database (CEROD).
A drop-in replacement for public-domain SQLite source code
that has the added ability to read database that has been both
compressed and encrypted.
$2000 one time fee More InfoBuy Now!
8. The ZIPVFS Read/Write Compressed Database Extension.
The ZIPVFS extension automatically compresses and encrypts
your data as it is written to disk, and decompressed and decrypts
it while reading.
$4000 one time fee More InfoBuy Now!
  1. SQLite License.
    Warranty of title and perpetual right-to-use for the SQLite source code.

    Cost: $6000 one time fee

    More Info

  2. SQLite Encryption Extension (SEE).
    A drop-in replacement for public-domain SQLite source code that has
    the added ability to read/write AES-encrypted databases.

    Cost: $2000 one time fee

    More Info

  3. Compressed And Encrypted Read-Only Database (CEROD).
    A drop-in replacement for public-domain SQLite source code
    that has the added ability to read database that has been both
    compressed and encrypted.

    Cost: $2000 one time fee

    More Info
    Buy Now!

  4. The ZIPVFS Read/Write Compressed Database Extension.
    The ZIPVFS extension automatically compresses and encrypts
    your data as it is written to disk, and decompressed and decrypts
    it while reading.

    Cost: $4000 one time fee

    More Info
    Buy Now!

Download & Install SQLite Package Installer

Installation packages available for Windows 10 users:

From the SQLite official website in the download section. The following screenshot allows you to download different SQLite’s installation packages for Windows:

The command line shell program:

The highlighted download package is called the Command-Line Program (CLP). CLP is a command line application that let you access the SQLite database management system and all the features of the SQLite. Using CLP, you can create and manage the SQLite database. And it is the tool that we will use throughout the tutorial.

  • 32-bit DLL(x86): The SQLite Database system core library for x86 platforms.
  • 64-bit DLL (x64): The SQLite Database system core library for x64 platforms.

Installing the Command-Line Program (CLP) on your machine:

In the following steps, you will find the steps for how to install the Command-Line Program (CLP) on your machine:

Step 1) Download the highlighted download package from the previous image to your PC. It is a “zip” file.

Step 2) Extract the zip file. You will find the “sqlite3.exe” in the extracted file as following:

Step 3) Open My Computer, and double-click the partition “C” to navigate to it:

Step 4) Create a new directory “sqlite“:

Step 5) Copy the file “sqlite3.exe” into it. This is what we will use through the tutorials to run SQLite queries:

However, there are some other packages for different purposes. They are not required. But you might need it if you are using a different OS than Windows you can get the Linux or Mac OS version of SQLite.

Also, you can get the documentation or source code from there if you wish. You can also get the API for Windows Phone 8 or .Net and other programming languages.

Here are some other different packages for different purposes:

  • The Source Code and some alternative Source Code Formats – The complete source code that made up the SQLite.
  • The documentation – The documentation of the SQLite as HTML pages. It is the same online documentation, but downloadable as HTML page so that you can open them offline.
  • Precompiled Binaries for Linux.
  • Precompiled Binaries for Mac OS X (x86).
  • Precompiled Binaries for Windows Phone 8 – SDK and components to develop an application for Windows Phone 8 that uses SQLite databases.
  • Precompiled Binaries for Windows Runtime – SDK and other components for developing an application to connect to SQLite databases for the Windows Runtime platforms.
  • Precompiled Binaries for .NET – these are some set of DLLs and .NET libraries that you can use them from .NET application to connect to SQLite databases.

About The SQLite Team

Paid support options and products are provided by
Hipp, Wyrick & Company, Inc., (Hwaci), a
with headquarters in

Charlotte, North Carolina and has been in business since
Hwaci has an international team of
employees and associates representing the best available talent.
We are a 100% engineering company. There is
no sales staff.
Our goal is to provide outstanding service and honest advice
without spin or sales-talk.

Hwaci is a small company but it is
also closely held and debt-free and has low
fixed costs, which means that it is largely immune to buy-outs,
take-overs, and market down-turns. Hwaci intends to
continue operating in its current form, and at roughly its current
size until at least the year 2050.
We expect to be here when you need us,
even if that need is many years in the future.

Building for sqlcipher

To run node-sqlite3 against sqlcipher you need to compile from source by passing build options like:

If your sqlcipher is installed in a custom location (if you compiled and installed it yourself),
you’ll also need to to set some environment variables:

Custom builds and Electron

Running sqlite3 through electron-rebuild does not preserve the sqlcipher extension, so some additional flags are needed to make this build Electron compatible. Your command needs these additional flags (be sure to replace the target version with the current Electron version you are working with):

In the case of MacOS with Homebrew, the command should look like the following:

mocha is required to run unit tests.

In sqlite3’s directory (where its resides) run the following:


  • Konstantin Käfer
  • Dane Springmeyer
  • Will White
  • Orlando Vazquez
  • Artem Kustikov
  • Eric Fredricksen
  • John Wright
  • Ryan Dahl
  • Tom MacWright
  • Carter Thaxton
  • Audrius Kažukauskas
  • Johannes Schauer
  • Mithgol


Thanks to Orlando Vazquez,
Eric Fredricksen and
Ryan Dahl for their SQLite bindings for node, and to mraleph on Freenode’s #v8 for answering questions.

is BSD licensed.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *