v.to.db: fix option=query #2085
Merged
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
metzm
added
bug
veroandreo
approved these changes
Jan 13, 2022
|
To be backported: 3f7bd7e |
neteler
pushed a commit
that referenced
this pull request
Jan 28, 2022
With `option=query`, query columns can not only be columns, but also SQL expressions like `count(x)` or `avg(x)`. In these cases the check for column type fails, and it is up to the user to first create a new column of the appropriate type for storing results, before running `v.to.db`.
|
Backport done |
ninsbl
pushed a commit
to ninsbl/grass
that referenced
this pull request
Oct 26, 2022
With `option=query`, query columns can not only be columns, but also SQL expressions like `count(x)` or `avg(x)`. In these cases the check for column type fails, and it is up to the user to first create a new column of the appropriate type for storing results, before running `v.to.db`.
ninsbl
pushed a commit
to ninsbl/grass
that referenced
this pull request
Feb 17, 2023
With `option=query`, query columns can not only be columns, but also SQL expressions like `count(x)` or `avg(x)`. In these cases the check for column type fails, and it is up to the user to first create a new column of the appropriate type for storing results, before running `v.to.db`.
neteler
pushed a commit
to nilason/grass
that referenced
this pull request
Nov 7, 2023
With `option=query`, query columns can not only be columns, but also SQL expressions like `count(x)` or `avg(x)`. In these cases the check for column type fails, and it is up to the user to first create a new column of the appropriate type for storing results, before running `v.to.db`.
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.
with
option=query, query columns can not only be columns, but also SQL expressions like count(x) or avg(x). In these cases the check for column type fails, and it is up to the user to first create a new column of the appropriate type for storing results, before runningv.to.db.