amitavaghosh1
amitavaghosh1
~/.config/nixpkgs/overlays 35s ❯ cat neovim-nightly.nix (1) 11:50:12 import (builtins.fetchTarball { url = https://github.com/nix-community/neovim-nightly-overlay/archive/master.tar.gz; }) ❯ nix-env -iA nixpkgs.neovim-nightly 11:49:34 unpacking 'https://github.com/nix-community/neovim-nightly-overlay/archive/master.tar.gz'... unpacking 'https://github.com/edolstra/flake-compat/archive/b7547d3eed6f32d06102ead8991ec52ab0a4f1a7.tar.gz'... unpacking 'https://api.github.com/repos/neovim/neovim/tarball/c977d8b43cd6ecf7ad756f9b064eadea79fbd604'... unpacking 'https://api.github.com/repos/numtide/flake-utils/tarball/997f7efcb746a9c140ce1f13c72263189225f482'... unpacking 'https://api.github.com/repos/nixos/nixpkgs/tarball/6d8215281b2f87a5af9ed7425a26ac575da0438f'... error:...
idm · master± ⟩ xo schema "mysql://[email protected]/users_dev?charset=utf8&parseTime=True&loc=Local" -o models/ error: sql: Scan error on column index 5, name "proc_def": converting NULL to string is unsupported This is from mysql:8 ....
Right now, if I want to analyze query cost, The explain statement, needs to be understood. And for complex queries it gets difficult to keep track of everything. It would...
`go env` ``` GO111MODULE="" GOARCH="amd64" GOBIN="/Users/amitava.ghosh/go/bin/" GOCACHE="/Users/amitava.ghosh/Library/Caches/go-build" GOENV="/Users/amitava.ghosh/Library/Application Support/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="darwin" GOINSECURE="" GOMODCACHE="/Users/amitava.ghosh/.asdf/installs/golang/1.18.3/packages/pkg/mod" GOOS="darwin" GOPATH="/Users/amitava.ghosh/.asdf/installs/golang/1.18.3/packages" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/Users/amitava.ghosh/.asdf/installs/golang/1.18.3/go" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/Users/amitava.ghosh/.asdf/installs/golang/1.18.3/go/pkg/tool/darwin_amd64" GOVCS="" GOVERSION="go1.18.3" GCCGO="gccgo" GOAMD64="v1" AR="ar" CC="clang"...
Obviously the examples provided are way to descriptive for a real world use. With already so much code we have to write in go, I don't think, I would like...
``` INSERT INTO `products` (`created_at`,`updated_at`,`deleted_at`,`code`,`price`) VALUES ("2022-12-13 03:09:51.724","2022-12-13 03:09:51.724",NULL,"D42",100) RETURNING `id` ``` syntax error at position 165 near 'RETURNING'