At the moment Nebraska relies heavily on gopkg.in/dat.v1 for communicating with its Postgresql database. That's inherited from the coreroller era.
However, both dat and logxi, its logging library, are not maintained since many years. So it's not possible to migrate dependent projects to Go modules, and it's unlikely that any upstream PRs against the projects could be merged.
We need to think about an option to replace dat with a Postgres driver which is widely used and actively developed, for example:
At the moment Nebraska relies heavily on gopkg.in/dat.v1 for communicating with its Postgresql database. That's inherited from the coreroller era.
However, both dat and logxi, its logging library, are not maintained since many years. So it's not possible to migrate dependent projects to Go modules, and it's unlikely that any upstream PRs against the projects could be merged.
We need to think about an option to replace dat with a Postgres driver which is widely used and actively developed, for example: