Changes to work in postgres #196
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @vitormattos thanks for the pull request. Could you please solve the conflict? I could then check if it still works on MySQL / SQLite databases. There are now some keywords in use like for example |
I believe the best way will be use QueryBuilder for all queryies but it will be a big refactor. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In PostgreSQL columns with double quote are interpreted literally.
I used Nextcloud 20.0.4, and when setup finished, all columns where created in lowercase.
To resolve this problem, I changed all columns to syntax without double quotes.
The WhichDownloader property was being used incorrectly when it was to be CURL. Adjustments were made to avoid errors.
I changed some places that were giving error for accessing array keys that didn't exist.