-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyColumn for Creating Query View #87
Comments
@iamtekson I would be happy to contiribute on this issue. |
Please contribute if you like. Thank you @iamMHZ |
I see this feature was removed in an earlier commit, and given the name it seems to have been a diliberate removal. What's the reason behind this / is there a way of reimplementing this feature? Without it I get errors later in my data pipeline, meaning I can't use this package to automate my work fully. If it's remaining removed, I would also suggest updating the documentation which implies the argument still exists. Thanks |
Hi @trodaway, thank you for raising this issue. I forgot exactly why we removed that feature, but I am going to add it again and try to see how it impact, rest of the things. If you want to send a PR, I am also happy to accept it. |
Just released the new version |
Thanks for taking a look at this so quickly. I think the |
Seems write permission is limited on this repo so can't push / do a PR. This is the code I've got:
|
Yes you are write. I will make another PR to solve this issue. Thanks again! |
Thanks for sorting! I assume 2.5.3 may take a couple of hours to get onto conda-forge, but should be good by tomorrow? I didn't see how fast it was yesterday. |
I already released the new version! |
Thanks - it just didn't come through onto conda-forge for another couple of hours. |
Yes, it takes few hours to create the build file for Conda. |
I found that your publish_featurestore_sqlview, does not have the primary key (
'<keyColumn>primary_key</keyColumn>'
) parameter. Is there a specific reason behind that?? Are you willing that the primary key(s) be recognized by GeoServer automatically?Also, I want to mention that a complex query can have a primary key made by combining more than one attribute. Is there a solution for handling that?
The text was updated successfully, but these errors were encountered: