1,100 karma · joined July 7, 2018
But overall it's a bit easier yes.
Also, SQLC doesn't allow for dynamic query building so think about an input search struct from which you may add where clauses — or not.
Also doesn't support multiple inserts with N rows being inserted.
Otherwise for standard queries, it's great.
> Conditional use() (unline current hooks)
> Support for Document Metadata
> Support for stylesheets
> Support for async scripts
> Support for Custom Elements
New chat comes in, they find related chats, and extract some instructions/context from these to feed into that new chat's context?
type CreateUser struct {
store storage.Store
cache caching.Cache
logger logging.Logger
pub events.Publisher
// etc
}func (op CreateUser) ServeHTTP(ctx, req, rw) {}
// or if you have custom handlers
func (op CreateUser) ServeHTTP(ctx, input) (output, error) {}
And in my main.go, or where I set up my dependencies, I create each operation, passing it its specific dependencies. I love that because I can keep all the helper methods for that specific operation/handler on that specific struct as private methods.
It does get tedious when you have one operation needing another, as you might start passing these around or you extract that into its own package/service.
How has this been solved in your opinion? Do you mean with recent versions with much bigger limits but also heaps more expensive?
e.g., fuzzy text matching => "fuzzy text matching"