#6325)

|      Q       |   A
|------------- | -----------
| Type         | bug
| Fixed issues | 

#### Summary

It seems PHP SQLite drivers allows `"` to be used to escape literal
values, but natively such syntax produces an sqlite parse error [1].

I have discovered this when analysing SQLite log, it is otherwise
tested.

I checked all other `"` in SQLite platform and manager and all of them
seems correct otherwise.

[1] https://dbfiddle.uk/KQAGp9Ea (notice the 2nd query is the same, but
uses `"` instead of `'`)

The list of reserved characters for cache key names was missing ':'

Spell which properly

Update UPGRADE.md

|      Q       |   A
|------------- | -----------
| Type         | improvement
| Fixed issues | none

#### Summary

Page:
https://www.doctrine-project.org/projects/doctrine-dbal/en/4.0/reference/types.html#bigint

The `int`-mapping needs to be added at
https://www.doctrine-project.org/projects/doctrine-orm/en/3.1/reference/basic-mapping.html#doctrine-mapping-types
too!

What is the right version information? Is it only working if you have
DBAL 4 **and** ORM 3?

To reduce Algolia operations and indexes older versions get removed

Remove older versions from the docs

* 3.8.x:
  Add MariaDB 11.3 to the test matrix (#6342)
  Spell which properly
  Fix double quote used wrongly for literal value in SqliteSchemaManager (#6325)

I forgot to remove it in e7aef4e.

I am also replacing the commented out connection parameters in
phpunit.xml.dist with a link to this paragraph because they have
diverged from the one we use in the CI since f88dc28.

Document how to run integration tests locally

<!-- Fill in the relevant information below to help triage your pull
request. -->

|      Q       |   A
|------------- | -----------
| Type         | bug
| Fixed issues | #6357

#### Summary

`PostgreSQLSchemaManager::_getPortableTableColumnDefinition()` is
modified to call the private method `parseDefaultExpression()` on
default values for `JSON` field to correctly normalize doubled
single-quotes in json string value.

A test to cover this case is added.

Follow-up to #6358 (@sbuerk): `getName()` is gone on 4.0.x. This change
will make merging this test up easier for us.

* 3.8.x:
  Avoid calling deprecated Type::getName() (#6359)
  Ensure correct json default value normalization (#6358)
  Document how to run integration tests locally
  Remove unused script

… connection (#6362)

|      Q       |   A
|------------- | -----------
| Type         | bug
| Fixed issues | N/A

#### Summary

When calling `Connection::setNestTransactionsWithSavepoints()`, the
platform is fetched to check if savepoints are actually supported. This
is a problem because it might cause the connection to be opened.

I've removed the check which will postpone the exception to the first
time we attempt to create a savepoint.

* 3.8.x:
  Connection::setNestTransactionsWithSavepoints() should not break lazy connection (#6362)
  [Docs] Update docs regarding "datetimetz" type (#6014)