Lann

Double check the query by passing the builder to https://godoc.org/github.com/Masterminds/squirrel#DebugSqlizer and printing the result.

There isn't enough context in your posts to answer. Try giving the full query and/or link to source

I merged a fix for that bug. Could you post the output of ToSql instead?

https://github.com/fermyon/spin-trigger-command/issues/7#issuecomment-2035572411 > Another option would be a e.g. `--sleep-forever-on-completion flag` that causes this trigger to...sleep forever on completion. If all its resources were dropped before sleeping this process would likely...

@evanphx > The interface value itself, being the 2 64bit quantities, will store the int itself and the type information. I previously (briefly) looked for documentation on `gc`'s optimizations trying...

We face a practical problem with `result`, `option`, and `tuple` types: they are parameterized *anonymous* types with no obvious ergonomic mapping to Go's type system _in all cases_. For example,...

If we want `result` error types to implement `error` we'll need a wrapper type in some cases, which would also be anonymous: ```wit // Errors a la `errno` write: func(buf:...

Given the above problems, I think generics are possibly the least-bad solution for `result`s and `option`s (and `tuple`s, though that's a separate issue) _[edit: in scenarios where we can't generate...

> There will be the exceptions, no doubt, and perhaps that's where generics could be used. Ah, apologies, this is exactly what I was suggesting; using generic forms of e.g....

Here is the current wasi-preview2 definition of (stream) `read`, which conveniently includes a problematic return type with an anonymous `tuple` nested in a `result`: https://github.com/bytecodealliance/wasmtime/blob/main/crates/wasi/wit/deps/io/streams.wit#L74-L78 > `-> result` In practice...