José Nieto
José Nieto
I added more test cases here: https://github.com/upper/db/pull/472 I hope one of them solves your problem. We won't remove the `Ping()` from `NewClone` yet, maybe in the future we'll use it...
@whisper-bye this is currently not possible and `exql` is an internal package. Would the sqlbuilder package work for your case? https://upper.io/db.v3/lib/sqlbuilder
@whisper-bye Maybe we'll need to rewrite the query. Which database are you using? Could you provide an example of the full query?
Hello @kipply, Is this case something that could be solved by using the `omitempty` option? That word tells upper to ignore the field when it has a zero value: ```go...
Hello @ptflp, could you elaborate on this point a little bit more?
Hello @c2h5oh, This looks a lot like: https://github.com/golang/go/issues/26332, in that issue we have a reference to https://golang.org/cl/170700, where they recommend this: > Most uses of the Valuer will be trivial,...
This sounds like a good suggestion, do you have an example on how to do that with PostgreSQL + Go?
v3 could be a good opportunity to break stuff and fix this.
With go1.13 we have a nice way to deal with errors (https://blog.golang.org/go1.13-errors), which is better than type checking. See the example below: ```go // A new error value adapterErr :=...
Hello @cmoad, Can you try setting ParentID to `*int64`?: ``` type Child struct { ID int64 `db:"id"` ParentID *int64 `db:"parent_id" } type ParentChild struct { ParentID `db:"pid"` Parent `db:",omitempty,inline"` Child...