feat: add db package

[ravisuhag]

Common package for connecting to SQL databases

[StewartJingga]

Since this is a pretty important part of an application (interacting with the main source) and we will use it across our odpf services, should we consider adding test? at least for migration and transaction.

wdyt?

[krtkvrm]

do we need these yaml & mapstructure tags here?

[ravisuhag]

So that when we compose this in a higher level config struct, we can tell viper what names to use in the configs passed through yaml file. Any other suggestion to achieve that?

[spy16]

I think this the best way to do it.

P.S.: I think, these kinds of tags are okay (even good) to be there for any struct even if you don't have immediate need -- They don't really have an inherent cost and when you actually need to use the struct to show/read yaml/json etc. it just works. (It just says "if you were to represent this in YAML, these are the key names you should be using")

[ravisuhag]

+1

[ravisuhag]

Since this is a pretty important part of an application (interacting with the main source) and we will use it across our odpf services, should we consider adding test? at least for migration and transaction.

wdyt?

@StewartJingga @krtkvrm Added high-level tests for both. Please check. Let me know if we need to make them more strict.