How to Read an ER Diagram: Tables, Keys, and Relationships Explained

·1 views

An entity-relationship (ER) diagram visually represents a database's tables, columns, and the connections between them. In such diagrams, boxes denote tables, bold headings indicate table names, and lines between boxes represent foreign-key relationships. Symbols at each end of a line specify the cardinality — one-to-one, one-to-many, or many-to-many — with the last type typically resolved using a join table. Common pitfalls include assuming all relationships are one-to-many, overlooking nullable columns, and misreading the direction of foreign keys. Tools like dbdiagram.io can auto-generate ER diagrams from a database connection string, making schema visualization accessible without manual effort.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

All-in-One WP Migration plugin flaw puts 5 million WordPress sites at risk

A critical second-order SQL injection vulnerability, tracked as CVE-2026-19949, has been discovered in the All-in-One WP Migration and Backup plugin version 7.109 and earlier, affecting over 5 million WordPress installations. Attackers can inject malicious payloads through public input vectors like trackbacks, which remain dormant in the database until an administrator triggers a backup restore or import operation. Once activated, the exploit can expose the site's secret key, enabling unauthenticated attackers to upload a malicious archive and achieve remote code execution. Developer ServMask released version 7.110 on August 20, 2026, to patch the flaw, but only around 35% of active installations had updated at the time of reporting. No large-scale active exploitation has been confirmed yet, and administrators are urged to update immediately, rotate secret keys, and audit past restore activity and database changes.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How engineer promotions really work at Google, Meta, Amazon and Microsoft

Engineers at major tech companies often stall in promotions not due to lack of skill but because the promotion process itself is poorly understood. Each company uses a distinct system: Google relies on a formal committee that reviews written packets and peer feedback, while Meta evaluates candidates twice a year through a performance cycle where consistent visible output every six months is critical. Amazon requires a written narrative tied to its Leadership Principles, reviewed by external bar raisers who can block promotions if results appear too recent or unproven. Every major tech company also has a 'terminal level' — such as Google's L5 or Meta's E5 — where career progression becomes optional and the nature of the role fundamentally shifts from individual execution to broader organizational impact. Understanding which process applies to your company and optimizing accordingly can be the difference between advancing and cycling through the same feedback for years.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How git reflog can recover commits after an accidental git reset --hard

A developer accidentally ran 'git reset --hard HEAD~3' in the wrong repository window, instantly wiping three commits from the working tree. Because Git does not immediately delete unreferenced commit objects, the work was recoverable using 'git reflog', which logs every position HEAD has pointed to and survives a reset. By identifying the correct commit hash in the reflog and running another 'git reset --hard' to that hash, all three commits were fully restored within seconds. The reflog only tracks committed work, however, meaning genuinely uncommitted changes lost to a hard reset have no recovery path. The developer now rehearses destructive Git operations on a disposable repository clone before running them on any codebase they care about.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Nine categories EM interviewers score you on — and how to prepare for all of them

Engineering manager interviews are scored across nine distinct categories, ranging from performance management and conflict resolution to technical judgment and vision, meaning strong preparation in only a few areas is rarely enough. Unlike individual contributor loops that test depth in a narrow technical domain, EM loops sample broadly, and gaps in even two categories can cost a candidate the offer. Most behavioural questions ultimately probe four things: whether the candidate ran a structured process, can name a specific tradeoff, owns outcomes without deflecting, and is clearly identifiable as the decision-maker within their own story. A practical preparation method involves writing down eight to twelve real situations from the past two years, mapping each to the nine categories, and identifying which cells remain empty — those gaps represent the questions most likely to catch a candidate off guard. Each story should then be rehearsed aloud, not memorised, targeting roughly ninety seconds and always ending with a candid reflection on what the candidate would do differently.

0 comments Read more at DEV Community