Surya Asriadie
Surya Asriadie
yes, correct, that exactly what will happen since `Begin` method in Adapter is actually returns another adapter with transaction connection, so it should be covered 👍
still wip but I've created poc for idea described above https://github.com/go-rel/primaryreplica
nice observation 👍 we should not need to check context in adapter, because it's taken care by repository. the flow is roughly like this: - when transaction is started, the...
> The first approach is more flexible (can be used in any context), however it doesn't allow us to differentiate between errors for stale and nonexistent records. Is this that...
> It it possible to change Delete() to accept mutates or must strong backward compatibility be maintained? It's okay, this shouldn't break the compilation, and REL is still in unstable...
Hi, thanks for using REL and reporting this, Currently REL checks if foreign and association key have the same key to prevent modifying association of other records. https://github.com/go-rel/rel/blob/9969ceac156830eae893e6be42918442a617e1d1/filter_query.go#L636-L651 but I...
Thank you, let me know if you have any question!
sounds important and need to be fixed do you have suggestion what to use other than map? maybe sorted slice? 🤔
although this may increase allocation due to internal linked list, this seems better and easier solution than using sorted slice 🤔 (feel free to work on this if you have...
I think a better way is to make existing `Mutation` and `Mutate` struct as linked list container as well, and we can keep the same field as is for now...