Previously in my fresher software developer time, I rarely write SQL, I always use ORM to wrap SQL. But time past and too much abstraction bites me. So I decide to only write SQL from now as much as possible, no more ORM for me. But if there is any cool ORM for Go, I guess I try.
This guide is not kind of guide which cover all cases. Just my little tricks when I work with SQL.
Use UUID instead. If you can, and you should, choose UUID type which can be sortable.
Stay away from all kind of database timestamp (MySQL timestmap, SQLite timestamp, ...) Just use int64 then pass the timestamp in service layer not database layer.
Why? Because time and date and location are too much complex to handle. In my business, I use timestamp in milliseconds. Then I save timestamp as int64 value to database. Each time I get timestamp from database, I parse to time struct in Go with location or format I want. No more hassle!
It looks like this:
[Business] time, data -> convert to unix timestamp milliseconds -> [Database] int64
You should use index for faster query, but not too much. Don't create index for every fields in table. Choose wisely!
For example, create index in MySQL:
CREATE INDEX `idx_timestamp`
ON `user_upload` (`timestamp`);
If compare with field which can be NULL, remember to check NULL for safety.
-- field_something can be NULL
-- Bad
SELECT *
FROM table
WHERE field_something != 1
-- Good
SELECT *
FROM table
WHERE (field_something IS NULL OR field_something != 1)
Need clarify why this happpen? Idk :(
VARCHAR or TEXT
Prefer VARCHAR if you need to query and of course use index,
and make sure size of value will never hit the limit. Prefer
TEXT if you don't care, just want to store something.
Plase read docs about online ddl operations before do anything online (keep database running the same time update it, for example create index, ...)