How do I avoid SQL injection using pgx?

To avoid SQL injection when using the pgx library in Go, it is essential to use parameterized queries. This allows the database to distinguish between code and data, preventing malicious data from being executed as part of a query. Below is an example of how to use pgx safely with parameterized queries.

package main import ( "context" "fmt" "log" "github.com/jackc/pgx/v4" ) func main() { conn, err := pgx.Connect(context.Background(), "your_connection_string") if err != nil { log.Fatalf("Unable to connect to database: %v\n", err) } defer conn.Close(context.Background()) var name string var id int32 = 1 err = conn.QueryRow(context.Background(), "SELECT name FROM users WHERE id=$1", id).Scan(&name) if err != nil { log.Fatalf("QueryRow failed: %v\n", err) } fmt.Printf("User name: %s\n", name) }

SQL injection pgx Go parameterized queries database security

Related Questions

How do I avoid rehashing overhead with std::set in multithreaded code?

How do I find elements with custom comparators with std::set for embedded targets?

How do I erase elements while iterating with std::set for embedded targets?

How do I provide stable iteration order with std::unordered_map for large datasets?

How do I reserve capacity ahead of time with std::unordered_map for large datasets?

How do I erase elements while iterating with std::unordered_map in multithreaded code?

How do I provide stable iteration order with std::map for embedded targets?

How do I provide stable iteration order with std::map in multithreaded code?

How do I avoid rehashing overhead with std::map in performance-sensitive code?

How do I merge two containers efficiently with std::map for embedded targets?