-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Comparing changes
Open a pull request
base repository: doctrine/dbal
base: 3.8.3
head repository: doctrine/dbal
compare: 3.8.4
- 11 commits
- 14 files changed
- 7 contributors
Commits on Mar 5, 2024
-
Fix double quote used wrongly for literal value in SqliteSchemaManager (
#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 `'`)
Configuration menu - View commit details
-
Copy full SHA for e33f663 - Browse repository at this point
Copy the full SHA e33f663View commit details
Commits on Mar 12, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9c2b00a - Browse repository at this point
Copy the full SHA 9c2b00aView commit details -
Merge pull request #6332 from greg0ire/witch-hunt
Spell which properly
Configuration menu - View commit details
-
Copy full SHA for 87785d8 - Browse repository at this point
Copy the full SHA 87785d8View commit details
Commits on Mar 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for e5db00e - Browse repository at this point
Copy the full SHA e5db00eView commit details
Commits on Apr 10, 2024
-
Configuration menu - View commit details
-
Copy full SHA for a527330 - Browse repository at this point
Copy the full SHA a527330View commit details
Commits on Apr 11, 2024
-
Document how to run integration tests locally
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.
Configuration menu - View commit details
-
Copy full SHA for d5d4ed5 - Browse repository at this point
Copy the full SHA d5d4ed5View commit details -
Merge pull request #6355 from greg0ire/doc-local-tests
Document how to run integration tests locally
Configuration menu - View commit details
-
Copy full SHA for 16cfdc8 - Browse repository at this point
Copy the full SHA 16cfdc8View commit details
Commits on Apr 16, 2024
-
Ensure correct json default value normalization (#6358)
<!-- 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.
Configuration menu - View commit details
-
Copy full SHA for e2a6621 - Browse repository at this point
Copy the full SHA e2a6621View commit details -
Configuration menu - View commit details
-
Copy full SHA for edbf307 - Browse repository at this point
Copy the full SHA edbf307View commit details
Commits on Apr 25, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ad2fee0 - Browse repository at this point
Copy the full SHA ad2fee0View commit details -
Connection::setNestTransactionsWithSavepoints() should not break lazy…
… 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.
Configuration menu - View commit details
-
Copy full SHA for b05e48a - Browse repository at this point
Copy the full SHA b05e48aView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 3.8.3...3.8.4