Skip to content

SequoiaStudios/DB1

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits

.gitignore

.gitignore

 
 

.travis.yml

.travis.yml

 
 

PACKAGECONTROL.md

PACKAGECONTROL.md

 
 

README.md

README.md

 
 

Repository files navigation

DB1 Documentation

Welcome to the DB1 Documentation.

As an introduction to DB1 (after installing), we'd highly suggest the Quick Start guide.

INDEX

Installation

If Package Control is already installed:

  1. Open the Sublime Text command palette ("Tools" > "Command Palette")
  2. Enter Package Control: Install Package
  3. Enter DB1

Congratulations! DB1 will now be installed. If you are not greeted with the DB1 installation message from Package Control, please restart Sublime Text.

If Package Control is not already installed, please follow the instructions for installation, and then follow the above instructions.

Quick Start

The first step to getting started is making sure that DB1 is installed. Once that's done, it might help to check out some of the commands available to DB1.

Once that's finished, the first big command is DB1: Connect to a Database. DB1: Connect to a Database initiates a connection for a single view in Sublime Text. This means that there's a one-to-one relationship of connections to views. Each connection is then tied to the database it's connected to, such that in view #1 you can execute queries on database 'A', and in View #2 you can execute queries on database 'B'.

When using the DB1: Connect to a Database you'll need to know the database type, username, host, port (if it's not the default) and password of the database you're connecting to. In cases like PostgreSQL authentication (where authentication is trust based) a password is not required.

To help streamline workflow, if there is not a connection active in the view, then running one of the DB1: Execute ... SQL will initiate the connection process before the query is then run.

Once you're connected, DB1 will prompt you with a list of databases to choose from. The database you select is the one you can now execute queries against. You can then change databases using the DB1: Change Database command.

Now that we're ready to run some queries, DB1 supports a couple different workflows.

  1. The Results Window Workflow

Using the command DB1: Execute SQL will open the Results Window. The Results Window allows for you to have a continuously open window to display query results. This contrasts the disposability of the Quick Query window, where results are lost when the window is closed.

Results Window

As you can see above, we are free to execute queries in the left view, while the results are displayed in the Results Window on the right.

A quick note: By default, when executing queries to the Results Window, after the query execution, the focus is changed to the Results Window. This can be annoying to some as you then have to reselect the query view on the left to write new queries. However, you can change this setting to leave the focus on the execution view.

In addition to the above setting, by default the contents of Results Window is deleted with every query, but that can be changed to either "prepend" or "append" the results.

This workflow tends to work really well if you'd like to be able to interact with results, as you can do things like search for text in the Results Window.

  1. The Quick Query view.

Using the command DB1: Execute Quick SQL will open the Quick Query view. The Quick Query view allows you to output the results of a query to a disposable (you can't save it, and when it's gone, you can't recover the contents) output view at the bottom of the window.

Quick Query view

This view is easy to use if you're just executing a quick SQL query and the query results don't have any sort of permanence.

Finally, regardless of the view that you choose, most aspects of the results are customizable. In the PostgreSQL query below, all possible options for query display are enabled.

DB1: Connected to alexggordon@10.0.1.195 using database alexggordon 

Query 1: Executed in 0.0143s. Executed at 2015-10-16 15:10:59.
Autocommit is off. Isolation Level Database Default. Deferrable Database Default. Readonly off. 
------------------
select * from pet;
------------------
+--------+---------+-------+
| name   | owner   |   age |
|--------+---------+-------|
| Libby  | Alex    |    16 |
+--------+---------+-------+

To associate the connected settings, see the items below for the associated settings.


DB1: Connected to alexggordon@10.0.1.195 using database alexggordon


Query 1:


Executed in 0.0143s.


Executed at 2015-10-16 15:10:59.


Autocommit is off.


Isolation Level Database Default.


Deferrable Database Default.


Readonly off.


------------------
select * from pet;
------------------


+--------+---------+-------+
| name   | owner   |   age |
|--------+---------+-------|
| Libby  | Alex    |    16 |
+--------+---------+-------+

After fully customizing you're results, you should be good to go!

Reporting Issues and Feature Requests

Please report all issues and feedback to the DB1 Issue and Request Tracker. All issues will be posted and followed there. In the event that Github is unavailable or extremely inconvenient, please email support@sequoiastudios.io

In addition to issues and feature requests, the documentation file used here is also hosted in that repository so as to track changes.

Changelog

V1.0.1

Improvements:
  • None.
Bug Fixes:
  • Removed Ubuntu dependency on Libpython that caused DB1 to not load on x64_86 Linux.

V1.0.2

Improvements:
  • You can now specify ports using user@host:port syntax.
  • Postgresql 8.1 and early have increased performance.
  • You can now customize all aspects of a connection in the "stored_connections" setting.
Bug Fixes:
  • Fixed a bug causing issues with older versions of postgresql.
  • Fixed a bug that caused DB1 to sometimes ignore ports that were manually changed.

V1.1.0

Feature Additions:
  • You can now connect to MariaDB and local SQLite databases through DB1.
Improvements:
  • Improved settings management and error correcting.
Bug Fixes:
  • Fixed 'null' port storage for some databases using the default port.
  • Fixed result window being reopened if the results window was in a separate window pane.
  • Fixed some connection timeout issues.

Commands

As a note, all commands make heavy use of the Sublime Text status bar located at the bottom of the screen. After a command is executed, the status bar is almost always updated with the result, and in the case of longer running commands (connecting, and query execution) a loading indicator will show.

Connect To Database

Command: db1_connect

This initiates a connection to a database. Required information is:

  • Database Type
  • db_username@host:port (:port is optional. If none is specified, then the default port will be used.)
  • password

If your database uses a custom port, you can also enter the port during the connection. You can do this when prompted for the address (user@host:port) and by appending the port onto the end of connection string after a : marker. The full connection string, with the optional port, should look similar to alex@hostname:1111.

After a connection is initiated, you will be prompted for the database you would like to use. You can select any database you'd like to, (you can always change later).

If there is an issue connecting, the error will be displayed at the bottom of your view.

For issues connecting, please see the connection issues section.

Remove Stored Connection

Command db1_remove_connection

This command removes a stored connection permanently.

Change Database

Command db1_use_database

This command allows a user to change the database. The user will be prompted with a list of databases available to change to, from which they can select the database they're prefer. If there is no active connection in the view, one will be created upon execution of the command.

Execute Sql

Command db1_execute_sql

This command executes sql and exports the results to the Results Window. The Results Window is simply a file to which query results are written. You can customize the location (and other aspects of the Results Window) of the file in your Settings.

By default, the Results Window will look like this upon query execution:

Results Window

The sql that this command executes can be passed to it through a couple of ways.

  • If there is no selection in the active view, then this command will parse and execute the entire view as sql.
  • If there a single selection in the view, then this command will just execute that text.
  • If there are multiple selections in the view, this command will parse the multiple selections for queries, and execute those queries.

The default setting is to erase the results window on every query execution. In addition to this, by default the focus will be moved to the Results Window after every query execution.

Execute Quick Sql

Command db1_execute_quick_sql

This command executes sql and exports the results to the Quick Query view (Sublime Text output window). This view is a disposable window located at the bottom of the screen.

Quick Query view

Execute Template

Command db1_execute_template

The db1_execute_template command is special in that it allows the user to execute any predefined sql, with any number of variables (0 - ∞). This command follows the format:

    {
        "keys": ["command+shift+1"],
        "command": "db1_execute_template",
        "args": {
            "mysql_pattern": "select * from %s;",
            "postgresql_pattern": "select * from %s;",
            "maria_pattern": "select * from %s;",
            "sqlite_pattern": "select * from %s;",
            "output_type": "quickpanel"
        }
    }

In the case of this command, there is one variable, represented by the %s. If the text pet was highlighted in a Sublime Text view (the Quick Query view doesn't count), and the keyboard shortcut command+shift+1 was run, then the sql statement

select * from pet;

would be run.

It's important to note that variables are not required for this command nor are multiple "_pattern" options required. To execute SQL against just a MySQL database, then just the "mysql_pattern" is required, like the following simpler version of the template.

    {
        "keys": ["command+shift+1"],
        "command": "db1_execute_template",
        "args": {
            "mysql_pattern": "select * from pet limit 100;",
            "output_type": "window"
        }
    }

The above command can be executed by the keyboard shortcut regardless of what text is highlighted, or the view you are currently in and will appear in the Results Window.

The final option in the shortcut is to choose the location of the output for this command. The two possibilities are:

  • "output_type": window Export the results of the query to the Results Window (pictured here)
  • "output_type": quickpanel Export the results to the disposable quickpanel (pictured here)

Commit Changes

Command db1_commit_changes

Connections to the database will default to either have autocommit on, or autocommit off. If autocommit is off, then any changes made to the database will not be permanent until they are committed. This command will commit those changes and make them permanent.

Rollback Changes

Command db1_rollback_changes

Connections to the database will default to either have enable autocommit , or disable autocommit. If autocommit is off, then any changes made to the database will not be permanent until they are committed. This command will rollback any changes made to the database.

Toggle Autocommit

Command db1_toggle_autocommit

This command will either disable autocommit or enable it. When the command is run, if you have previously toggled autocommit, the menu will show you the currently set value.

Set Isolation Level

Command db1_set_isolation_level

This command will allow you to change the isolation level of your current PostgreSQL or SQLite connection

PostgreSQL:

The values are:

  • Read uncommitted
  • Read committed
  • Repeatable read
  • Serializable

To read more about PostgreSQL isolation levels, please check out the PostgreSQL documentation.

SQLite:

The values are:

  • None
  • DEFERRED
  • IMMEDIATE
  • EXCLUSIVE

For SQLite, autocommit is tied into isolation level. When the isolation level is set to None, then autocommit is turned on, however, all other isolation levels disable autocommit for SQLite.

Set Deferrable (PostgreSQL Only)

Command db1_set_deferrable

This command will either disable the deferrable status of the PostgreSQL connection. When the command is run, if you have previously toggled the deferrable status, the menu will show you the currently set value.

This defaults to the database default for the connection

Set Readonly (PostgreSQL Only)

Command db1_set_readonly

This command will either disable the readonly status of the PostgreSQL connection. When the command is run, if you have previously toggled the readonly status, the menu will show you the currently set value.

If the connection is set to readonly then changes cannot be made to the database. This defaults to the database default for the connection.

Open Results Window

Command db1_open_results_window

This command opens the Results Window. The Results Windows stores the output of the queries executed by the db1_execute_sql command. If there is no active connection in the view, one will be created upon execution of the command.

Open Documentation Command

Command db1_open_documentation

The command opens the DB1 documentation.

Report Issue Command

Command db1_report_issue

The command opens the DB1 Issue and Feature Tracker.

Connection Issues

One of the more common connection issues is connections timing out. By default the connection timeout for a new connection is 5 seconds. You can change the amount of time a connection takes to timeout in the settings (see the stored connections setting for examples).

Settings

To edit your personal DB1 settings, please navigate to:

"Preferences" > "Package Settings" > "DB1" > "Settings - User"

If you would like to see the default options, please see the file at:

"Preferences" > "Package Settings" > "DB1" > "Settings - Default"

REMEMBER, the default settings are routinely reset. While saving your user settings there may temporarily work, please save them in the user settings mentioned above.

Stored Connections

"stored_connections":
{
    "user@1.1.1.1":
    {
        "database_type": "MySQL",
        "password": "hunter2",
        "port": 3306,
        // settings below are optional. The setting they will default to is shown. 
        // 'DEFAULT' refers to the database default for the setting. 
        "autocommit": false,
        // connection timeout in seconds
        "connection_timeout": 5,
    },
    "user@localhost":
    {
        "database_type": "PostgreSQL",
        "password": "",
        "port": 5432,
        // settings below are optional. The setting they will default to is shown. 
        // 'DEFAULT' refers to the database default for the setting. 
        "autocommit": false,
        "connection_timeout": 5,
        // optional, postgresql only settings
        "isolation_level": 'DEFAULT', // can be 0, 1, 2, or 3. 
        "readonly": false,
        "deferrable": 'DEFAULT'
    }
}

Stored Connections are where all stored user database connections go. They are automatically stored through the db1_connect command. If you have a custom port to use, you can update the connection manually, using following the syntax:

"stored_connections":
{
    "database_type": "MySQL",
    "password": "password",
    "port": 3306
}

Or when using the db1_connect command, you can append the port onto the end of the connection string, like:

user@host:port

In general all field are required, in the case of password-less PostgreSQL authentication, please leave the password field as an empty string (password: "").

If you use SSH tunneling to connect to your database, please use the local port of the SSH tunnel in the settings.

Set Syntax on Execute

Default Setting:

"set_syntax_on_execute": True

When set to true, if a view does not have a syntax file assigned to it when executing SQL, then DB1 will set the syntax of the view to the relevant sql file (either PostgreSQL or MySQL).

Results Table Format

Default Setting:

"results_table_format": "psql"

The Results Table Format defines the appearance of the box around the just the query results. This applies to both the Results Window and Quick Query view.

Available Options when executing the query select * from pet;

  • "grid"
+--------+---------+-------+
| name   | owner   |   age |
+========+=========+=======+
| Libby  | alex    |    16 |
+--------+---------+-------+
  • "fancy_grid"
╒════════╤═════════╤═══════╕
│ name   │ owner   │   age │
╞════════╪═════════╪═══════╡
│ Libby  │ alex    │    16 │
╘════════╧═════════╧═══════╛
  • "psql" (default)
+--------+---------+-------+
| name   | owner   |   age |
|--------+---------+-------|
| Libby  | alex    |    16 |
+--------+---------+-------+
  • "pipe"
| name   | owner   |   age |
|:-------|:--------|------:|
| Libby  | alex    |    16 |
  • "orgtbl"
| name   | owner   |   age |
|--------+---------+-------|
| Libby  | alex    |    16 |
  • "simple"
name    owner      age
------  -------  -----
Libby   alex        16
  • "plain"
name    owner      age
Libby   alex        16
  • "html"
<table>
<tr><th>name  </th><th>owner  </th><th style="text-align: right;">  age</th></tr>
<tr><td>Libby </td><td>alex   </td><td style="text-align: right;">   16</td></tr>
</table>

Show DB1 Header

Default Setting

"show_db1_header": true

At the top of the Results Window and Quick Query view, there is a header that looks like this:

DB1: Connected to user@host using database adventure_land

This setting defined whether or not that header shows.

Show Query

Default Setting:

"show_query": true

By default, above the query results, the query currently being executed is shown. This setting defines whether or not the query is shown.

Query Table Format

Default Setting:

"query_table_format": "simple"

This setting only applies if the "show_query" setting is true. It defines the appearance of the query displayed.

Available Options when executing the query select * from pet;

  • "grid"
+--------------------+
| select * from pet; |
+--------------------+
  • "fancy_grid"
╒════════════════════╕
│ select * from pet; │
╘════════════════════╛
  • "psql"
+--------------------+
| select * from pet; |
+--------------------+
  • "pipe"
|:-------------------|
| select * from pet; |
  • "orgtbl"
| select * from pet; |
  • "simple" (default)
------------------
select * from pet;
------------------
  • "plain"
select * from pet;
  • "html"
<table>
<tr><td>select * from pet;</td></tr>
</table>

Show Query Number

Default Setting:

"show_query_number": true

By default, the number of the query being executed is show in front of each query. For example, when executing 2 queries, "Query 1" will show in front of the first query, and "Query 2" will show in front of the second query. This controls the display of that.

Show Query Execution Time

Default Setting:

"show_query_execution_time": true

By default, this will show the amount of time it took to execute the query. The format will follow:

"Executed in 0.0016s."

Show Execution Datetime

Default Setting:

"show_execution_datetime": true

By default, this will show the date and time the query was executed at. The format will follow:

"Executed at 2015-10-08 10:45:55."

Datetime Format

Default Setting:

"datetime_format": "%Y-%m-%d %H:%M:%S"

This setting only applies if the "show_execution_datetime" setting is true. It defines the format of the date and time.

We strongly recommend using strftime.org to format this.

If this is formatted incorrectly, nothing will be displayed.

Show Autocommit Status

Default Setting:

"show_autocommit_status": true

By default, this will show the status for the connection. This defaults to the database default, for all database types.

If Autocommit is "off", then any changes must be committed or rolled back before they have a permanent effect.

If the connection is closed (Sublime Text is quit, or internet connection is lost), all changes will be rolled back.

Show Isolation Level (PostgreSQL only)

Default Setting:

"show_isolation_level": false

Will not show by default. When set to true this will show the isolation level of the connection.

PostgreSQL:

Show isolation level will show one of the following:

  • Isolation Level Database Default.
  • Isolation Level Read Committed.
  • Isolation Level Repeatable Read.
  • Isolation Level Serializable.
  • Isolation Level Read Uncommitted.
SQLite:

Show isolation level will show one of the following:

  • Isolation Level None
  • Isolation Level Deferred
  • Isolation Level Immediate
  • Isolation Level Exclusive

The isolation level for both database types can be changed through the Set Isolation Level command.

Show Deferrable Status (PostgreSQL only)

Default Setting:

"show_deferrable_status": false

Will not show by default. When set to true this will show the deferrable status of the connection. It will show one of the following:

  • Deferrable Database Default.
  • Deferrable On.
  • Deferrable Off.

The deferrable status can be changed through the Set Deferrable command.

Show Deferrable Status (PostgreSQL only)

Default Setting:

"show_readonly_status": true

By default, this shows the readonly status of the connection. It will show one of the following:

  • Readonly Database Default.
  • Readonly On.
  • Readonly Off.

The deferrable status can be changed through the Set Readonly command.

Align Numbers

Default Setting:

"align_numbers": "decimal"

This setting controls how numbers (and the corresponding columns headers) are aligned in the results tables. The available options are:

  • "right" right align all numbers
  • "center" center align all numbers
  • "left" left align all numbers
  • "decimal" align all numbers along the decimal point (or where the decimal point would be for whole numbers)

Align Strings

Default Setting:

"align_strings": "left"

This setting controls how text (and the corresponding columns headers) are aligned in the results tables. The available options are:

  • "right" right align all text
  • "center" center align all text
  • "left" left align all text
  • false do not align text

Erase Results Window

Default Setting:

"erase_results_window": true

By default, on every query execution the results window is erased. Changing this setting to false means that the results will either be prepended or appended to the Results Window depending on the results window append style.

Focus Results Window on Execution

Default Setting:

"focus_results_window_on_execution": true

By default, when executing queries, the Results Window will come into focus. However, when simply scrolling through the results, this "feature" can be annoying, so by setting this to false, the focus will not be changed upon query execution.

Results Window Append Style

Default Setting:

"results_window_append_style": "append"

This setting only applies if "erase_results_window" is set to false. Depending on your workflow, some people prefer to append query results (put new results at the end of the Results Window) or prepend (put new results at the beginning of Results Window) the results.

Available options:

  • "append" (default)
  • "prepend"

Results Window Location Osx

Default Setting:

"results_window_location_osx": "/tmp/results.txt"

We recommend care when changing this setting, as Sublime Text needs write access to this location. This is simply the location of the Results Window. every time a query is executed to the Results Window, the file is saved.

Results Window Location Windows

Default Setting:

"results_window_location_windows": "C:\\WINDOWS\\TEMP\\results.txt"

When changing this setting, please escape backslashes

We recommend care when changing this setting, as Sublime Text needs write access to this location. This is simply the location of the Results Window. every time a query is executed to the Results Window, the file is saved.

Results Window Location Linux

Default Setting:

"results_window_location_linux": "/tmp/results.txt"

We recommend care when changing this setting, as Sublime Text needs write access to this location. This is simply the location of the Results Window. every time a query is executed to the Results Window, the file is saved.

Key Bindings

Custom Sublime Text key bindings are defined in "Preferences" > "Key Bindings - User" setting.

By default there are only two default DB1 commands.

On OSX they are:

  • { "keys": ["command+shift+e"], "command": "db1_execute_sql" }
  • { "keys": ["command+shift+r"], "command": "db1_execute_quick_sql" }

and Linux and Windows:

  • { "keys": ["ctrl+shift+e"], "command": "db1_execute_sql" }
  • { "keys": ["ctrl+shift+r"], "command": "db1_execute_quick_sql" }

All other DB1 commands (listed below) can be set in the "Key Bindings - User" file mentioned above and must follow the format:

{ "keys": ["command+o"], "command": "open_file" }

The only exception to the above is the db1_execute_template command. This command is special in that it allows the user to execute any predefined sql, with any number of variables. This command follows the format:

    {
        "keys": ["command+shift+1"],
        "command": "db1_execute_template",
        "args": {
            "mysql_pattern": "select * from %s;",
            "postgresql_pattern": "select * from %s;",
            "maria_pattern": "select * from %s;",
            "sqlite_pattern": "select * from %s",
            "output_type": "window"
        }
    }

In the case of this command, there is one variable, represented by the %s. If the text pet was highlighted in a Sublime Text view (the Quick Query view doesn't count), and the keyboard shortcut command+shift+1 was run, then the sql statement

select * from pet;

would be run in the current view. As usual, if there is no connection active in the view, you will be prompted to initiate one.

It's important to note that variables are not required for this command, and an indefinite number of variables can be used. For more information, see the db1_execute_template documentation.

All DB1 Commands:

  • db1_connect
  • db1_use_database
  • db1_remove_connection
  • db1_execute_sql
  • db1_execute_quick_sql
  • db1_execute_template
  • db1_commit_changes
  • db1_rollback_changes
  • db1_toggle_autocommit
  • db1_set_isolation_level
  • db1_set_readonly
  • db1_set_deferrable
  • db1_open_results_window
  • db1_open_documentation
  • db1_report_issue

License Information

Entering Your License

To enter your license, first you need to purchase one. If you've done that (yay), then the next step is to open the DB1 User Settings file at:

"Preferences" > "Package Settings" > "DB1" > "Settings - User"

You then need the three pieces of information (db1_license_name, db1_license_email, and db1_license_code) included in the license email you received.

After it's entered, your settings file should look similar to this:

{
    "db1_license_code": "DB1-A98U5-A98U5-A98U5-A98U5",
    "db1_license_email": "support@sequoiastudios.io",
    "db1_license_name": "Sequoia Studios"
}

Then place those in the DB1 user settings file (remember, you can't modify the license email or name after purchasing). If you receive a message like:

error

Then you may have forgotten a comma, colon, or quotation mark after one of the elements.

If for some reason you've followed the above, and are still getting the unregistered message, email us with your purchasing information and we'll get it fixed ASAP.

Recovering a Lost License

To recover a lost license key please email us with the name, license email address and quantity of licenses purchased. We'll get your licenses to you as fast as the minions allow.

Alternative Payment

As an alternative to payment for DB1, we would be more than happy to supply you with a license upon proof of a donation of $29.99 (USD) or more to Will Bond. This software wouldn't be possible without his work on packagecontrol, and his original idea and implementation of a Sublime Text database client.

Bulk Discounts

If you, like us, enjoy saving money, send us an email at support@sequoiastudios.io with the quantity of licenses you'd like to purchase, and any other incentives you can throw in. We're up for a good negotiating session.

Refunds

So DB1 sucks for you. Sorry about that. Email us and we'll refund you as soon as possible. Let us know if there's anything we can do to mitigate that though.

Educational Discount

We'd love to be able to help out students, so if you are one, send us an email from your student account, with the projects or classes you'd like to use DB1 for, and we'll work something out!

Tax Information

Why do we charge tax in Massachusetts? Because unfortunately since we're an LLC registered in Massachusetts, we have to charge tax on any goods we sell, including digital goods. If the tax annoys you, shoot us an email when you're in Massachusetts and we'll buy you a beer to make up for it.

For any EU customers that are subject to VAT tax, while it's regrettable that we do this at this point, we don't currently support charging or reporting VAT tax. Please follow your local laws regarding this.

Other

For all other inquiries please email support@sequoiastudios.io (you're probably seeing a pattern now). Be kind though, Brian works through a lot of email every day :).

Open Source Libraries Used

DB1 Uses several open source libraries in its code. These licenses are also distributed with DB1 and can be found in the root DB1 folder in a folder called licenses.

Please report any issues with the licenses to the issues page

In no particular order:

Pymysql

Licensed under MIT License.

Copyright (c) 2010, 2013 PyMySQL contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Psycopg2

Licensed under LGPL

psycopg2 and the LGPL
=====================

psycopg2 is free software: you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published
by the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

psycopg2 is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Lesser General Public
License for more details.

In addition, as a special exception, the copyright holders give
permission to link this program with the OpenSSL library (or with
modified versions of OpenSSL that use the same license as OpenSSL),
and distribute linked combinations including the two.

You must obey the GNU Lesser General Public License in all respects for
all of the code used other than OpenSSL. If you modify file(s) with this
exception, you may extend this exception to your version of the file(s),
but you are not obligated to do so. If you do not wish to do so, delete
this exception statement from your version. If you delete this exception
statement from all source files in the program, then also delete it here.

You should have received a copy of the GNU Lesser General Public License
along with psycopg2 (see the doc/ directory.)
If not, see .


Alternative licenses
====================

If you prefer you can use the Zope Database Adapter ZPsycopgDA (i.e.,
every file inside the ZPsycopgDA directory) user the ZPL license as
published on the Zope web site, http://www.zope.org/Resources/ZPL.

Also, the following BSD-like license applies (at your option) to the
files following the pattern psycopg/adapter*.{h,c} and
psycopg/microprotocol*.{h,c}:

 Permission is granted to anyone to use this software for any purpose,
 including commercial applications, and to alter it and redistribute it
 freely, subject to the following restrictions:

 1. The origin of this software must not be misrepresented; you must not
    claim that you wrote the original software. If you use this
    software in a product, an acknowledgment in the product documentation
    would be appreciated but is not required.

 2. Altered source versions must be plainly marked as such, and must not
    be misrepresented as being the original software.

 3. This notice may not be removed or altered from any source distribution.

Sqlparse

Licensed under BSD License.

Copyright (c) 2009, Andi Albrecht 
All rights reserved.

Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:

    * Redistributions of source code must retain the above copyright notice,
      this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright notice,
      this list of conditions and the following disclaimer in the documentation
      and/or other materials provided with the distribution.
    * Neither the name of the authors nor the names of its contributors may be
      used to endorse or promote products derived from this software without
      specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Tabulate

Licensed under the MIT License.

Copyright (c) 2011-2015 Sergey Astanin

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

FuzzyFileNav

Licensed under the MIT License.

License
Fuzzy File nav is released under the MIT license.

Copyright (c) 2012 - 2015 Isaac Muse isaacmuse@gmail.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

About

The official issue and feature request tracker for DB1

sequoiastudios.io

Resources

Readme
Activity
Custom properties

Stars

7 stars

Watchers

5 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

No packages published