Issue Description

What was unclear/insufficient/not covered in the documentation

How to update and increment in one single query

If possible: Provide some suggestion on how we can enhance the docs

Add this to the docs.

Additional context

#7268

Issue Template Checklist

Issue type:

[x] question
[ ] bug report
[ ] feature request
[x] documentation issue

Database system/driver:

[ ] cordova
[x] mongodb
[ ] mssql
[ ] mysql / mariadb
[ ] oracle
[ ] postgres
[ ] cockroachdb
[ ] sqlite
[ ] sqljs
[ ] react-native
[ ] expo

TypeORM version:

[x] latest
[ ] @next
[ ] 0.x.x (or put your version here)

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

Details for the issue

What did you do?

1. Enter simple query, e.g. select 1;
2. Press ENTER key many times that query from step

There is very little documentation available for the source code. As such, the source is highly difficult to understand and interpret by others. Please consider adding in appropriate documentation as soon as possible.

Documentation should be updated for database creation on MacOS (using Swift 4.2)

Link to affected documentation section: https://github.com/stephencelis/SQLite.swift/blob/master/Documentation/Index.md#read-write-databases

try FileManager.default.createDirectoryAtPath(
path, withIntermediateDirectories: true, attributes: nil

should become:
try FileManager.default.createDirectory(

The on-line demo at http://kripken.github.io/sql.js/examples/GUI/ does not give error messages (for wrong SQL or missing tables or attributes).
The version of @lovasoa does: http://lovasoa.github.io/sql.js/GUI/

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

In the tutorial events there is this example:

const User = bookshelf.model('User', {
  tableName: 'users',

  initialize() {
    this.on('saving', (model) => {
      return User.forge({email: model.get('email')}).fetch().then((user) => {
        if (user) 
            throw new Error('That email address already exists')
    

Given that we support CURRENT_TIMESTAMP, the lack of CURRENT_DATE feels like an omission. While you can hack it with date(now), I keep finding myself wishing there was a direct way to reference this. Given that now means CURRENT_TIMESTAMP, I think there's precedent for today meaning CURRENT_DATE. This is supported by all backends we support (and is in the ISO standard I believe).

Is your feature request related to a problem? Please describe.
Provide help in CLI for sub-commands

Describe the solution you'd like
Sub-commands help should describe the sub-command's functionality and options available for the sub-command

Describe alternatives you've considered
N/A

Additional context
See: golang-migrate/migrate#370

Via this image: https://github.com/neilotoole/xcgo

It is possible to produce a bunch of multi-platform release artifacts.

neilotoole/xcgo's companion example project sqlitr, via goreleaser, publishes a trivial sqlitr query tool in these forms:

• brew
• scoop
• snap
• deb
• rpm
• docker
• tarball

Note snap. Not trivial to do... `sna

How to recreate

• Preview a page that has content stored in contentblocks.

• When previewing a page that has content stored in contentblocks, the contentblocks do not show.

Expected behaviour

The contentblocks showing exactly as they do on the saved webpage

Error

With strict_variables: true, the error that is given is

Key "block" for array with keys "textsection" do

While it's sometimes valuable to know how a project has developed, there is usually little justification for including this information in the README, and certainly not immediately after other key information such as "what does this package do, and who might want to use it?"

Might I recommend that the feature history is migrated to an Appendix in the documentation?

requeryVersion = '1.6.0'
requeryVersion = '1.6.1'

E/BaseViewModel: java.sql.SQLNonTransientConnectionException
    io.requery.PersistenceException: java.sql.SQLNonTransientConnectionException
        at io.requery.sql.EntityDataStore.checkConnectionMetadata(EntityDataStore.java:588)
        at io.requery.sql.EntityDataStore$DataContext.getTransactionMode(EntityDataStore.java:747)

Originally posted by @dimitri in https://github.com/dimitri/pgloader/timeline

That's good thinking, and I think that's relevant for another PR. The PR introducing the statistics singleton should also take care of the following bits of refactoring of the code:

• the singleton is named “state” as I initially though I would update the global state of the migration to be able to know

DB.Updateable<t_stock_document>().SetColumns(k => new t_stock_document() { OutQTY = k.OutQTY - delDoc.F_Qty ?? 0, OutFinish = false }).Where(k => k.F_ID == delDoc.RelateID).ToSql();

语句中，使用??生成的Sql语句如图，运行时会报错 ，我以为是运算符优先级问题，
再加了括号试试，同样会报错，是否不支持??运算符
![TIM截图

I would like to propose adding README file as a description to explain potential users that basic sample is as basic as possible and more complicated scenarios they can find in storio-sample-app module

As of first congrats for this package - I'm using it quite often & it's a great help.

I'd like to ask a feature request - add support for MSSQL DB.
The main official mode of connection recommended by MS is ODBC/PDO.
[https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-2017#microsoft-odbc-driver-17-for-sql-server](ht

With options like "Open table" that basically do a SELECT * FROM table ...
"Alter table" Generate ALTER SQL in a tab.

Currently for table it says that the table has to be a string.

table

    (str) Used for many-to-many relationship only in order to specify the name of the intermediate table.

However it doesn't mention that it appears to follow the same form as the table attribute in entity classes, in the sense that you can pass it a tuple to specify the schema for databases like Postgresql.