feat: Implement pgx support

[hound672]

Hello. The frist attempt to implement pgx support. For now there is no any unittests, example is weird and so on. I just wonder if I am on the right way.

[hound672]

remove main.go, docker-compose. write unittests for transaction and for settings.

---

sqlmock cannot be used here due to different interfaces so I used pgxmock lib

[maranqz]

I'll take a closer look at the weekend.

[hound672]

Looks like pgxmock does not work on go1.13. I had the same issues with go1.13.

[maranqz]

If it's true, mark it in README.md and add skip test for old version of Go. GORM adapterfor example.

[hound672]

If it's true, mark it in README.md and add skip test for old version of Go. GORM adapterfor example.

Ok, I'll try. So this an another reason why I think that separated repositories is a good option.

[maranqz]

1. I see in pgx repo This is the previous stable v4 release. v5 been released. Is v4 still actual? https://github.com/jackc/pgx/tree/v4.18.1

2. Let's call the adapter pgx v4 to show the version explicitly.

[hound672]

1. I see in pgx repo This is the previous stable v4 release. v5 been released. Is v4 still actual? https://github.com/jackc/pgx/tree/v4.18.1
2. Let's call the adapter pgx v4 to show the version explicitly.

In the package's name? Like pgx -> pgx_v4?

[hound672]

1. I see in pgx repo This is the previous stable v4 release. v5 been released. Is v4 still actual? https://github.com/jackc/pgx/tree/v4.18.1
2. Let's call the adapter pgx v4 to show the version explicitly.

added v5 as well

[hound672]

Linter: I checked with 1.49 linter version and there are no any issues. And I will not modify files in trmanager.

[maranqz]

Linter: I checked with 1.49 linter version and there are no any issues. And I will not modify files in trmanager.

I'm fixing it)

[hound672]

Linter: I checked with 1.49 linter version and there are no any issues. And I will not modify files in trmanager.

I'm fixing it)

It's pretty strange) what's wrong?)

[maranqz]

golangci-lint version is 1.56, I think something changed in it.

I excluded mock dirs.

[hound672]

golangci-lint version is 1.56, I think something changed in it.

I excluded mock dirs.

I see, excluding. But why does it work before these changes?

[maranqz]

I think, cause is updating of exhaustruct: from 2.3.0 to 3.1.0 https://github.com/golangci/golangci-lint/blob/master/CHANGELOG.md#v1540

[hound672]

Pgx v5 works only with 1.19 and higher (due to generics). But in example should be two flags:

1. Works only with real db
2. Build only with 1.19 and higher.

[maranqz]

Build only with 1.19 and higher.

Use for pgxv5

//go:build go1.19,with_real_db
// +build go1.19,with_real_db

Space-separated elements	// +build pro enterprise	pro OR enterprise
Comma-separated elements	// +build pro,enterprise	pro AND enterprise
Exclamation point elements	// +build !pro	NOT pro

[hound672]

done. Actions passed after changes (in my env).

[coveralls]

Pull Request Test Coverage Report for Build 5915867691

• 221 of 239 (92.47%) changed or added relevant lines in 8 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.3%) to 94.015%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pgxv4/settings.go	39	42	92.86%
pgxv5/settings.go	40	43	93.02%
pgxv4/context.go	12	18	66.67%
pgxv5/context.go	12	18	66.67%
<!--	Total:	221	239	92.47%	-->

Totals
Change from base Build 5857614173:	-0.3%
Covered Lines:	1461
Relevant Lines:	1554

---

💛 - Coveralls

[maranqz]

Do you want to fix something else in the PR? I think PR is ready to merge. Good job and thank you for your work👍🎉🚀.

[hound672]

Do you want to fix something else in the PR? I think PR is ready to merge. Good job and thank you for your work👍🎉🚀.

Thanks!) Could you merge? Since I'm not authorized for that

[maranqz]

I will bump version of the lib in first September weekend.