This is the first Golang video I’ve seen that actually walks through concurrency with a *real* use case. Most use trivial examples that I didn’t find helpful. Also really appreciate how Lane leaves his errors in the video and talks through how he solves them. MUCH more useful than just showing perfect code. Less experienced devs will encounter basic errors, and seeing the thought process behind solving them is very valuable. Truly a top tier Golang tutorial, thank you for devoting the time to do this.
Sqlc and goose is a combination I've been excited to put together and did it on my own for a bit. I like the two because no ORM, reported excellent performance, typesafe queries, raw SQL to stay familiar with sql (i.e. no magic from ORMs) and simplicity.
I'm getting this error trying to install sqlc: error: cc1.exe: sorry, unimplemented: 64-bit mode not compiled in I'm on windows. Do you have any ideas how to get around this?
So glad I ran into this channel. It would be great if you could make a video focused more backend development with Go. For instance, I know what an interface, struct, slice, etc is but how and when do you use them when working on a real-world backend application? The video could be something like "Go for backend development" or something else
Great video, thanks. I've built JSON REST APIs in Go before, but I've never used sqlc or goose. I'm looking forward to using those tools in my next project...
The simpler way to add json tags to the struct generated by sqlc is to add this one line to sqlc.yaml "emit_json_tags: True': go: emit_json_tags: True out: "internal/database" Hope it helps.
you got my subscription for this video. i never see golang in real use case before. thanks for make this video happens. If could, please help make video about GO programming basic to advance.
Nice tutorial, thanks! One thing: if you add emit_json_tags: true to the sqlc.yaml file, you don't have to transform the fields manually in the models.go
Hello, thank you very much for this video. The only thing I would ask to help with is to find that text instruction file you are mentioning. Could not find is through the links. Thanks
Just finished wathcing the tutorial and I find it amazing! it tackles a lot of topics and the way you are explaining things makes them clear in my opinion. I have a question though, why are we taking the approach to create a new handler signature (authedHandler type) and not stick with the regular signature of (ReponseWriter, *Request) and just pass the authed user via a context to the children? This way if for example we wanted to have a chain of middlewarres and create an abstraction to call our middlewares with the handler we could rely on the fact that all middlewares have the same signature: func(http.Handler) http.Handler. I get that this would add extra complexity to the tutorial and would be out of scope. But im curious to see your way of thinking or if I am missing anything
Hey Lane ! Was looking for a video on this playlist which covered the context package of go Lang . However I couldn't find one , so could u please make one for us ! M quite sure plenty of subscribers like me want to understand contexts . U make things easy to understand 😁
Would a project like this make for a backend portfolio project ? When looking at building portfolio projects there is more to show in the front end than the backend .
Like and Sub. Tried few lessons for doing project step-by-step to learn. This is best one I found. Simple, but effective and understandable. Thank you for video. P.S. I made my response codes more accurate and used the HTTP library.
SQLC installation gives me this error: cc1.exe: sorry, unimplemented: 64-bit mode not compiled in Searched hours and unable to find what's wrong. Any help appreciated
This is the first Golang video I’ve seen that actually walks through concurrency with a *real* use case. Most use trivial examples that I didn’t find helpful.
Also really appreciate how Lane leaves his errors in the video and talks through how he solves them. MUCH more useful than just showing perfect code. Less experienced devs will encounter basic errors, and seeing the thought process behind solving them is very valuable. Truly a top tier Golang tutorial, thank you for devoting the time to do this.
glad you liked it!
This course is so good!
Followed until the end.
Looking forward to the next tutorial!
Sqlc and goose is a combination I've been excited to put together and did it on my own for a bit. I like the two because no ORM, reported excellent performance, typesafe queries, raw SQL to stay familiar with sql (i.e. no magic from ORMs) and simplicity.
I'm getting this error trying to install sqlc: error: cc1.exe: sorry, unimplemented: 64-bit mode not compiled in
I'm on windows. Do you have any ideas how to get around this?
@@NphiniT try putting the error in chatgpt or Gemini and see what it says. Otherwise, I use wsl2 for my dev work and that's where I installed it
@@nanonkay5669 Oh good idea 😅. Haven't used chatGPT since last year 😂🤣
@@nanonkay5669 Switched to WSL2. I think I'll do all my development here form now on. Thanks
@@NphiniT Sounds like maybe you didn't install them correctly. Did you do the installation just as how it appeared in the documentation?
So glad I ran into this channel.
It would be great if you could make a video focused more backend development with Go. For instance, I know what an interface, struct, slice, etc is but how and when do you use them when working on a real-world backend application? The video could be something like "Go for backend development" or something else
Be sure to sign up on Boot.dev for more of that kind of content
Upto 2:04 is prerequisites (can add this timestamp in the video as well!)
Updated thanks!
FINALLY THE VIDEO I WAS WAITING FOR
quick overview on that contexts are in go at: 1:08:58
This tutorial was brilliant. Thank you so much!
Great post! You are a legend ❤
Wow, thanks
Great video, thanks. I've built JSON REST APIs in Go before, but I've never used sqlc or goose. I'm looking forward to using those tools in my next project...
Lane dropping golden nuggets!
Glad you like it!
The simpler way to add json tags to the struct generated by sqlc is to add this one line to sqlc.yaml "emit_json_tags: True':
go:
emit_json_tags: True
out: "internal/database"
Hope it helps.
good call!
Thank you so much
Your backend course looks solid. I'm only interested in the Go related parts though. Will be signing up in a few days.
you got my subscription for this video. i never see golang in real use case before. thanks for make this video happens. If could, please help make video about GO programming basic to advance.
Thank you very much for the knowledge!
i really liked this format, learned a lot!
Thank you kindly
Nice tutorial, thanks! One thing: if you add emit_json_tags: true to the sqlc.yaml file, you don't have to transform the fields manually in the models.go
agreed, but also I sometimes like the separation of concerns that comes with not tying the models strictly together sometimes
Hello, thank you very much for this video. The only thing I would ask to help with is to find that text instruction file you are mentioning. Could not find is through the links. Thanks
sql.NullString{ Valid: item.Description != "", String: item.Description } can also be used :)
You are insane ❤🔥
Quite sane I assure you
Just finished wathcing the tutorial and I find it amazing! it tackles a lot of topics and the way you are explaining things makes them clear in my opinion.
I have a question though, why are we taking the approach to create a new handler signature (authedHandler type) and not stick with the regular signature of (ReponseWriter, *Request) and just pass the authed user via a context to the children? This way if for example we wanted to have a chain of middlewarres and create an abstraction to call our middlewares with the handler we could rely on the fact that all middlewares have the same signature: func(http.Handler) http.Handler.
I get that this would add extra complexity to the tutorial and would be out of scope. But im curious to see your way of thinking or if I am missing anything
Am on windows anytime i run sqlc generate i keep getting an error, postgres cant run on windows
how do i fix that
WSL 2
thanks for the video.
I'd dockerize that and keep it running :)
Hey Lane ! Was looking for a video on this playlist which covered the context package of go Lang . However I couldn't find one , so could u please make one for us ! M quite sure plenty of subscribers like me want to understand contexts . U make things easy to understand 😁
PS C:\Users\HP\Desktop\go> sqlc generate
# package postgres
schema.sql:1:1: the PostgreSQL engine does not support Windows.
What to do??
ask chatgpt
Join the discord for help :)
I know this may be a bit too late, and that you've probably already got your answer, but try to use WSL (Windows Subsystem for Linux)
@@Alex-hy7nx I'm using it in a docker container. it's easier
Would a project like this make for a backend portfolio project ? When looking at building portfolio projects there is more to show in the front end than the backend .
Absolutely. You could use GenAI to build the UI super super basic just to make it a little easier to reason about for the viewers of the project.
Great 👏🏻
I'm not able to connect to the database through DB_URL
Join the discord to get help :)
Like and Sub.
Tried few lessons for doing project step-by-step to learn. This is best one I found. Simple, but effective and understandable. Thank you for video.
P.S. I made my response codes more accurate and used the HTTP library.
Finished!
Interesting what kind of query cheaper in GetPostsForUser with JOIN or with subquery.
SQLC installation gives me this error: cc1.exe: sorry, unimplemented: 64-bit mode not compiled in
Searched hours and unable to find what's wrong. Any help appreciated
We will be able to help in the discord!
@@bootdotdev Link to the discord please
Great tutorial!
thanks a lot for the tutorial
Thank you!!!!
You're welcome!
hey, I got a error and its says that >The PostgreSQL does not support windows. what to do ?
Honestly... Use linux
use docker
or just use wsl
Is there a GitHub repo?
All the code is on Boot.dev!
Thank you lane
You're welcome!
29:20
43:10
Moore Sandra Williams Elizabeth Harris Betty
Thank you so much 👍👋👌🫡🙏🏻👏🤝😎✌️🫰🏻
You're welcome!
Is there a reason to prefer "go build && ./rssagg" over "go run ." ?
I prefer to build because it perfectly mimics production, but tbh doesn't matter much