This PR includes one breaking change:
- The `Provider.Exec` function now returns 2 values instead of only the error, the extra argument is the number of affected rows.
This PR also adds:
- CI with tests and linter
- Dockertest for making tests easier to run not only on CI but also on local machines for contributors
- Some bug fixes: Now we are handling a few edge cases better:
* If a struct has duplicated ksql tag names we will return an error instead of failing silently
* If a struct has no ksql tags we will return an error instead of failing on the query
* If a struct has attributes with no ksql tags they will be safely ignored instead of causing an error
* If a jointed table struct has an extra attribute with no `tablename` tag it will be ignored too because having an error for this would be more confusing than just ignoring it.
This change was finally made because the Delete function was the
only helper function that was not returning the ksql.ErrRecordNotFound
when no rows were found.
The other reason for this change is that we the most common use case is
by far for deleting a single element, and the philosophy of the library
is to optimize for the most common use-cases.
For making it easier to write queries for deleting many items
as well as many other less common use cases we
are already implementing the `kbuilder` package which is a
query builder.
This was done for a few different reasons:
1. This allows us to work on top of the pgx client in the future
2. This would allow our users to implement their own DBAdapters
to use with our tool.
3. This gives the users the option of using advanced configs
of any sql client they want to use and just feed us with it
after the configuration is done, which means we will not have
to worry about supporting a growing number of configurations
as we try to add support to more drivers or if we get issues
asking for more advanced config options.
