Methodology and editorial policy
How a record gets made, what the fields mean, and what we do when something changes.
Where facts come from
Only from the vendor's own public pages: product pages, pricing pages, documentation, official repositories and official issue trackers. Third-party reviews, listicles and AI answers are not sources for records. Every record lists its sources with the date each page was read.
Evidence labels
- Vendor pricing page / product page / documentation: the vendor's own statement. It describes what the vendor offers; it isn't an independent test.
- Source repository: license and activity read from the project's repository.
- Official project issue: used for status (for example, a proposed feature), never as proof a feature exists.
- Editorial judgment: "good fit" and "watch for" notes, guide recommendations and groupings. Always labeled.
"Not verified"
If a page didn't state something, or a vendor's site blocked our retrieval, the field says "not verified". Filters never treat "not verified" as a match. A missing database in a list means we didn't see it named, not that the tool can't connect to it.
Prices
We copy prices as published: amount, currency, billing period and unit. We don't convert currencies or average plans. "Quote only" means the vendor lists "contact sales". If a vendor's page localizes prices to the reader's location, we leave the price out rather than guess the US figure.
Model levels and features
Conceptual, logical and physical support, reverse engineering, DDL generation, compare/sync and Git integration are recorded when the vendor's pages describe them. Some vendors use different terms; any mapping we make is noted on the record.
Updates and corrections
- Source pages are re-fetched on a schedule and whenever someone reports a change. Pages whose text changed are reviewed by hand before a record is edited.
- Substantive changes (ownership, status, editions, prices, features) are logged on the change log with a date. Guide pages show an update history; their "updated" date changes only for substantive edits.
- Send corrections to info@datamodelingtools.com with a link to the vendor page. We correct verified errors and note it in the log.
Limitations
Vendor pages describe intended capabilities. They can be out of date, vague about which edition includes what, or written for marketing. We haven't used these tools hands-on for the records, so trial anything before you commit.
Independence and money
No vendor pays to be listed, ranked or described. There are currently no affiliate links. If we join an affiliate program, affected links will be marked, and this page will list the program.