Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrage to virtual-schema-common version 9.0.0 #35

Closed
AnastasiiaSergienko opened this issue Apr 6, 2020 · 1 comment
Closed

Upgrage to virtual-schema-common version 9.0.0 #35

AnastasiiaSergienko opened this issue Apr 6, 2020 · 1 comment
Assignees
@AnastasiiaSergienko
Labels
feature Product feature

Comments

@AnastasiiaSergienko
Copy link
Contributor

No description provided.

@AnastasiiaSergienko AnastasiiaSergienko added the feature Product feature label Apr 6, 2020
@AnastasiiaSergienko AnastasiiaSergienko self-assigned this Apr 6, 2020
AnastasiiaSergienko added a commit that referenced this issue Apr 6, 2020
@AnastasiiaSergienko
#35: updated to a new vscommon version
0517250
AnastasiiaSergienko added a commit that referenced this issue Apr 6, 2020
@AnastasiiaSergienko
#35: changed the version because the previous release breaks the inte…
8463324 
…rface
AnastasiiaSergienko added a commit that referenced this issue Apr 9, 2020
@AnastasiiaSergienko
#35: removed the KEYS keyword from generated queries because Exasol c…
c24fa10 
…an't parse it correctly
AnastasiiaSergienko added a commit that referenced this issue Apr 16, 2020
@AnastasiiaSergienko
#35: fixed sonar findings
5281567
AnastasiiaSergienko added a commit that referenced this issue Apr 16, 2020
@AnastasiiaSergienko
#35: improved test coverage
da0f89a
AnastasiiaSergienko added a commit that referenced this issue Apr 16, 2020
@AnastasiiaSergienko
#35: updated to a new vscommon version (#36)
6982a40 
* #35: updated to a new vs common version
* #35: changed the version because the previous release breaks the interface
* #35: removed the KEYS keyword from generated queries because Exasol can't parse it correctly
@AnastasiiaSergienko
Copy link
Contributor Author

Closed with #36

AnastasiiaSergienko added a commit that referenced this issue Apr 16, 2020
@AnastasiiaSergienko
#35: fixed errors after merge from master
84bf043
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AnastasiiaSergienko AnastasiiaSergienko

Labels
feature Product feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AnastasiiaSergienko