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.

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

Remove array_remove() for supporting PostgreSQL 9.2 #253

Merged
merged 1 commit into from
Aug 12, 2020

Conversation

k1LoW
Copy link
Owner

@k1LoW k1LoW commented Aug 12, 2020

Fix #251

Remove array_remove for supporting PostgreSQL 9.2.

@k1LoW k1LoW self-assigned this Aug 12, 2020
@codecov
Copy link

codecov bot commented Aug 12, 2020

Codecov Report

Merging #253 into master will decrease coverage by 0.80%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #253      +/-   ##
==========================================
- Coverage   68.89%   68.08%   -0.81%     
==========================================
  Files          22       22              
  Lines        3687     3694       +7     
==========================================
- Hits         2540     2515      -25     
- Misses        902      939      +37     
+ Partials      245      240       -5     
Impacted Files Coverage Δ
drivers/postgres/postgres.go 76.97% <100.00%> (+0.39%) ⬆️
datasource/datasource.go 22.22% <0.00%> (-12.70%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1927771...9092a4a. Read the comment docs.

@k1LoW k1LoW marked this pull request as ready for review August 12, 2020 16:30
@k1LoW k1LoW merged commit bc412b4 into master Aug 12, 2020
@k1LoW k1LoW deleted the remove-array_remove branch August 12, 2020 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

panic: runtime error: invalid memory address or nil pointer dereference
1 participant