Nice stuff Alexey! thanks for this link, haven't seen it so far.
Seems like we both got frustrated from the same issues with existing
solutions :-)
We took pretty different approaches to solve the typed-ORM problem though.
The reform library has a larger run-time content, and keeps the generated
code minimal, which is a very nice idea!
However, as it seems to me, there are still a lot of interface{}s, and
strings to pass to the library functions, which I try to avoid. The current
proposed orm implementation leaves zero guessing - the user does not need
to know column names, SQL queries, expressions or types. All the functions
are fully typed, which leaves no room for run-time bugs. I intend to keep
it like that as much as possible.
I would love to hear your opinion about it, and if you could enlighten me
with obstacles I will find in future development of this library, since it
seem like you have some experience in this field.
Cheers!
On Saturday, December 23, 2017 at 9:21:09 PM UTC+2, Alexey Palazhchenko
wrote:
>
> Hi,
>
> There is also https://github.com/go-reform/reform.
>
> –-–
> Alexey «AlekSi» Palazhchenko
>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
