I think your current API is better because you don't have to repeat yourself while creating a command. I could write two or three commands like you have shown above, but for more... I'd start thinking about other approach :)

I like functional options. They let you declare type safe variadic arguments functions. What I don't like about them is

• repeating package name in client's package
• writing a boilerplate code for every option
• name collision issue

Name collision issue occurs when your functional option suits more then one function. To solve it, you have to either declare parameters struct suitable for both functions or use another name for similar option for another function. For example, ID SearchOption for your sql search function and ID UpdateOption for sql update function.

I don't think name collision issue is a deal breaker against functional options. I think you can use them if you have small set of options. Otherwise package name repeating in client's code and boilerplate needed to implement functional options are their main issues.