Not possible to update context inside hooks

[Hades32]

As the current hook signature is func beforeHook(ctx context.Context, resource string, operationName string) error (and after hook even slimmer), it is only possible to read but not possible to write (without hacks) to the context.

Before starting a PR: Is there a reason why the signature is not func beforeHook(ctx context.Context, resource string, operationName string) (newCtx ctx context.Context, err error)?

I understand this would be a breaking change, but without this, the context use-case is pretty limited...

[aarondl]

I'd be curious what the use case is for having a hook modify the context. In general you can always achieve this by storing a map or a pointer in the context before a hook is ever called (in your code before you call your sqlboiler methods).

[Hades32]

So, as far as I understood, it's not good practice to modify an existing context (that's why there is no Set() method) - but this is currently our workaround, too.

Our concrete use-case, as discussed in #525, was tracing execution times, where we would place e.g. start time in the context in before and would use it in after. Generally any use-case that needs non-model specific data between hooks, would need that.

Generally if the driver below SQLBoiler has features that rely on context (e.g. request specific timeouts), then the hack above would not be sufficient.

[aarondl]

Because it's a breaking change we need to either wait or gate it behind some generation-time flag that will be deprecated in the new version (if that's possible). I'd accept a PR for this so long as it was non-breaking.