Sticky notes, comments, or discussions?
DrawSQL gives you three ways to put words on a diagram. The right one depends on what the words are for: documenting the schema, explaining the design, or settling a question with your team.
Table & column comments: documentation that's part of the schema itself. They appear as a small icon on the diagram (hover to read) and ship with your SQL export. If the next developer should read it in the database, it belongs here.
Sticky notes: explanations that live on the canvas. Use them for domain labels, design rationale, or anything the team should read without hovering. They show up in image exports and never touch your schema or SQL.
Discussions: conversations meant to end. Start a thread on a table, group, or sticky note (or diagram-wide), hash it out with the team, and resolve it once the question's answered. Reach for one when you need an answer, not an artifact.
Rules of thumb
Documenting what a column actually stores: use a column comment. It ships with your DDL.
Explaining a design decision everyone should see: put a sticky note next to the tables involved.
Asking why something exists, or reviewing a teammate's change: start a thread.
When a thread settles something worth keeping, copy the conclusion into a comment or sticky note, then resolve it.
A good test: will this matter in six months? If not, it's a thread. Resolve it and move on. If it will, write it down where it lasts: a column comment if it belongs in the database, a sticky note if it belongs on the canvas.