Downloads:

205,151

Downloads of v 3.25.2:

6,194

Last Update:

9/27/2018

Package Maintainer(s):

Software Author(s):

  • D. Richard Hipp
  • SQLite contributors

Tags:

sql sqlite db database embedded foss cross-platform

SQLite

This is not the latest version of SQLite available.

3.25.2 | Updated: 9/27/2018

Downloads:

205,151

Downloads of v 3.25.2:

6,194

Maintainer(s):

Software Author(s):

  • D. Richard Hipp
  • SQLite contributors

SQLite 3.25.2

This is not the latest version of SQLite available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install SQLite, run the following command from the command line or from PowerShell:

>

To upgrade SQLite, run the following command from the command line or from PowerShell:

>

To uninstall SQLite, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade sqlite -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade sqlite -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure sqlite installed
  win_chocolatey:
    name: sqlite
    state: present
    version: 3.25.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'sqlite' do
  action    :install
  version  '3.25.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: sqlite,
    Version: 3.25.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller sqlite
{
   Name     = 'sqlite'
   Ensure   = 'Present'
   Version  = '3.25.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'sqlite':
  provider => 'chocolatey',
  ensure   => '3.25.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install sqlite version="3.25.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 9/27/2018.

Description

SQLite is a software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine.

This package also installs sqlite tools by default - sqldiff, sqlite3, sqlite3_analyzer.

Features

  • Transactions are atomic, consistent, isolated, and durable (ACID) even after system crashes and power failures.
  • Zero-configuration - no setup or administration needed.
  • Full-featured SQL implementation with advanced capabilities like partial indexes, indexes on expressions, JSON, and common table expressions. (Omitted features)
  • A complete database is stored in a single cross-platform disk file. Great for use as an application file format.
  • Supports terabyte-sized databases and gigabyte-sized strings and blobs. (See limits.html.)
  • Small code footprint: less than 500KiB fully configured or much less with optional features omitted.
  • Simple, easy to use API.
  • Written in ANSI-C. TCL bindings included. Bindings for dozens of other languages available separately.
  • Well-commented source code with 100% branch test coverage.
  • Available as a single ANSI-C source-code file that is easy to compile and hence is easy to add into a larger project.
  • Self-contained: no external dependencies.
  • Cross-platform: Android, *BSD, iOS, Linux, Mac, Solaris, VxWorks, and Windows (Win32, WinCE, WinRT) are supported out of the box. Easy to port to other systems.
  • Sources are in the public domain. Use for any purpose.
  • Comes with a standalone command-line interface (CLI) client that can be used to administer SQLite databases.

Package parameters

  • /NoTools - Do not install sqlite tools

Example: choco install sqlite --params "/NoTools"


legal\License.txt
## SQLite Is Public Domain

All of the code and documentation in SQLite has been dedicated to the [public domain](http://en.wikipedia.org/wiki/Public_Domain) by the authors. All code authors, and representatives of the companies they work for, have signed affidavits dedicating their contributions to the public domain and originals of those signed affidavits are stored in a firesafe at the main offices of [Hwaci](http://www.hwaci.com). Anyone is free to copy, modify, publish, use, compile, sell, or distribute the original SQLite code, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

The previous paragraph applies to the deliverable code and documentation in SQLite - those parts of the SQLite library that you actually bundle and ship with a larger application. Some scripts used as part of the build process (for example the "configure" scripts generated by autoconf) might fall under other open-source licenses. Nothing from these build scripts ever reaches the final deliverable SQLite library, however, and so the licenses associated with those scripts should not be a factor in assessing your rights to copy and use the SQLite library.

All of the deliverable code in SQLite has been written from scratch. No code has been taken from other projects or from the open internet. Every line of code can be traced back to its original author, and all of those authors have public domain dedications on file. So the SQLite code base is clean and is uncontaminated with licensed code from other projects.


## Obtaining An License To Use SQLite

Even though SQLite is in the public domain and does not require a license, some users want to obtain a license anyway. Some reasons for obtaining a license include:

*   Your company desires warranty of title and/or 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 domain.
*   You want to hold a tangible legal document as evidence that you have the legal right to use and distribute SQLite.
*   Your legal department tells you that you have to purchase a license.

If you feel like you really need to purchase a license for SQLite, [Hwaci](http://www.hwaci.com/), the company that employs all the developers of SQLite, will [sell you one](http://www.hwaci.com/cgi-bin/license-step1). All proceeds from the sale of SQLite licenses are used to fund continuing improvement and support of SQLite.

## Contributed Code

In order to keep SQLite completely free and unencumbered by copyright, all new contributors to the SQLite code base are asked to dedicate their contributions to the public domain. If you want to send a patch or enhancement for possible inclusion in the SQLite source tree, please accompany the patch with the following statement:

> _The author or authors of this code dedicate any and all copyright interest in this code to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this code under copyright law._

We are not able to accept patches or changes to SQLite that are not accompanied by a statement such as the above. In addition, if you make changes or enhancements as an employee, then a simple statement such as the above is insufficient. You must also send by surface mail a copyright release signed by a company officer. A signed original of the copyright release should be mailed to:

> Hwaci  
> 6200 Maple Cove Lane  
> Charlotte, NC 28269  
> USA
legal\VERIFICATION.txt
VERIFICATION

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to

   x32: https://sqlite.org/2018/sqlite-dll-win32-x86-3250200.zip
   x64: https://sqlite.org/2018/sqlite-dll-win64-x64-3250200.zip
   Toolsx32: https://sqlite.org/2018/sqlite-tools-win32-x86-3250200.zip

   to download the files.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: 6CBC1467C392953E27D2CB719CF43549A46633DD0649FF56CF0BA283FFFED12A
   checksum64: 1694DC168BF9FE4C8CBE470903E5C89A5AED6E026C35DC65D7760A50F40EA872
   checksumTools32: 54F7C9E073E67680C7222B39130C86606AC6071C6D0A60C97D1802F593042CD4

File 'license.txt' is obtained from the following URL (and converted to markdown):
   http://www.sqlite.org/copyright.html
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path $MyInvocation.MyCommand.Definition
$embedded_path = if ((Get-OSArchitectureWidth 64) -and $env:chocolateyForceX86 -ne 'true') {
         Write-Host "Installing 64 bit version"; Get-Item "$toolsDir\*dll*win64*.zip"
} else { Write-Host "Installing 32 bit version"; Get-Item "$toolsDir\*dll*win32*.zip" }

$packageArgs = @{
    PackageName  = 'sqlite'
    FileFullPath = $embedded_path
    Destination  = $toolsDir
}
Get-ChildItem $toolsDir\* | Where-Object { $_.PSISContainer } | Remove-Item -Recurse -Force #remove older package dirs
Get-ChocolateyUnzip @packageArgs

$pp = Get-PackageParameters
if (!$pp.NoTools) {
    Write-Host "Installing tools"
    $packageArgs.FileFullPath = Get-Item "$toolsDir\*tools*win32*.zip"
    Get-ChocolateyUnzip @packageArgs
}

Remove-Item $toolsDir\*.zip -ea 0
tools\sqlite-dll-win32-x86-3250200.zip
md5: F1BBCA0D4C66B6D6CCAD58CB6217F01F | sha1: 461AEB0E6D738FE66229FDD93D94850346894B35 | sha256: 6CBC1467C392953E27D2CB719CF43549A46633DD0649FF56CF0BA283FFFED12A | sha512: CCA2338D20F7D1277627D946AEB68025CE544C136A50FB358C87E0950A3D1493D3C82D0DF0DBE4028B17C07BFAB156F2F0EE6BC5E82F623EA2A5CAB769036B54
tools\sqlite-dll-win64-x64-3250200.zip
md5: 1E648D818CA54E3AA20EC2ACE03C1B7A | sha1: 9FAD624C1AA1C0C9BA20230F2E176FAC305EDAC5 | sha256: 1694DC168BF9FE4C8CBE470903E5C89A5AED6E026C35DC65D7760A50F40EA872 | sha512: A925871A53D29E66628203919E0A2FB16B988F1B8E2BE19473804E3FECDBA047D0352EC1A12C29D74871642C10AAFF9CA1FA3E88ADFDB4101C66D157CC5022F9
tools\sqlite-tools-win32-x86-3250200.zip
md5: 03107C86D9BE12A9367D018B87F4C085 | sha1: 39EF9709972AF563768A121C2372F0CD868364CF | sha256: 54F7C9E073E67680C7222B39130C86606AC6071C6D0A60C97D1802F593042CD4 | sha512: CA5009C58AE46E12A89FC9052BB75E15B5AA3B15926E7280834195AB689563DAB2B1B53805D93E7047796FD4D90FB377861711512752417104064872A0FA3B67

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
SQLite 3.30.0 1318 Saturday, October 5, 2019 Approved
SQLite 3.29.0 12914 Thursday, July 11, 2019 Approved
SQLite 3.28.0 14323 Wednesday, April 17, 2019 Approved
SQLite 3.27.2 9623 Tuesday, February 26, 2019 Approved
SQLite 3.27.1 3671 Saturday, February 9, 2019 Approved
SQLite 3.27.0 872 Friday, February 8, 2019 Approved
SQLite 3.26.0 9206 Sunday, December 2, 2018 Approved
SQLite 3.25.3 3808 Tuesday, November 6, 2018 Approved
SQLite 3.25.2 6194 Thursday, September 27, 2018 Approved
Discussion for the SQLite Package

Ground Rules:

  • This discussion is only about SQLite and the SQLite package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or SQLite, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus