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.
During the development of my project, I came across the need to execute a multi-table join using sqlx.This resulted in arbitrary column names in the result set. I aimed to scan the resulting rows into a slice of structs containing embedded structs with
db
tagging.Unfortunately, I was unable to find any documentation for such a scenario. (I did see the "known issues" section of the readme)
After forking sqlx , replacing the package in my go mod file with my local version, debugging, and experimenting, I was able to achieve the desired result after a considerable amount of time.
In the interest of helping others who may encounter similar issues, I suggest extending the readme usage with an example directory that provides additional examples of not-so-straightforward scenarios. This will be beneficial for those adopting this package into their projects.