locking-center VS dynaQ

https://github.com/freakmaxi/locking-center Centralized locking service

I wouldn’t consider it idiomatic Go (and not something I recommend for use in production), but for fun, I built dynaQ (an abbreviation for dynamic querier) as a PoC of an extension to the database/sql core package erasing the need to model your DB results or use an ORM. There’s minimal reflection used to keep things performant, you can pass in an option whenever creating the new dynamic querier to auto-detect a time value from your database with a custom format (or take it’s default), and more.

But that’s why I built dynaQ. No need to pre-model your returns and it’s just as performant as the standard library ;)

I don’t have a contributor guide written for either of them, but feel free to help with the few issues in either this or this package I’ve written and released. They’re super simple things, but I’ve been rather busy at work and in life. So I haven’t had the time to address them. If you want to contribute, feel free to send me a DM with any questions!! Otherwise, just fork the repo(s) and just open a PR once you’re ready for the changes to be merged. I’ll review it asap!!

Nice!! Looks like a great companion to this module that I wrote and released recently!!

As far as projects to study go, I’ll start off with a shameless plug of two Go packages I’ve written, myself. This one is for converting between RGB (and other color space formats) to the nearest matching DMC thread color. This one is admittedly an extremely unidiomatic package (it’s completely opposite of how you should do things in Go) for supporting dynamic queries in Go without headaches or pre-defining “model” structs to hold each row of your query results. It’s something that can be useful, but it’s also built to showcase making the language work for a use case it wasn’t originally meant to support. If you wanna take a look at them, feel free. Also, I suggest looking at the testify repo. It’s an EXTREMELY popular testing library, and it’s also structured well.

I’ve created a package as an extension of the database/sql package in the stdlib for supporting dynamic queries without headaches in Go without having to predefine the structs. So you might be able to take some pointers from how I accomplished this

A couple of days ago, someone asked about why using dynamic queries in Go was such a headache. And after reading through the comments, looking at code, and studying others’ frustrations with this issue, I decided to tackle it. And that’s how dynaQ was born!!

It’s called dynaQ. It allows you to use dynamic queries on a database, with database transactions, and more, without having to pre-define any model structs to hold the returned data. It also allows for variable query arguments, as well as the ability to use custom time formats in your database and configure that format whenever creating a dynamic querier. Take a look and give it a shot!! I think you’ll be pretty pleased with the result