Of course, it will match on table name but also on table comment or table constraint names and declarations (primary key, foreign key, unique indexes, indexes or checks). Even if you don’t really know the table name, the search is the way to go. In case the table you are looking for is not already listed, the usual way to start is by searching it. In Azimutt, you see nothing, except a welcome message listing the (probably) most relevant tables to discover and a search field to begin your exploration journey. This is also possible in other ERDs, they call this database reverse engineering but here comes the most visible difference: once your database schema is loaded, traditional ERDs display all the tables and relations, but not Azimutt. Let’s see what this means.Ĭontrary to traditional ERDs, with Azimutt you don’t create your entities and relations from a blank canvas, but you are expected to load your existing database schema. This means, instead of showing the diagram right away, it let you explore it in a convenient way, showing only what is necessary not to overload you. This is why visual tools, like Azimutt, exist: to help developers but also data analysts or data scientists explore and understand the databases they are working with.Īzimutt is inspired by entity relationship diagrams (ERD) but it’s very different because it’s meant to handle already existing huge databases, not draw you first idea of database schema. With time, the number of tables and relations stored increase and, at some point, it may be hard to remember all of them. For traditional web applications, it’s done in collaboration with a relational database which handle the persistence part. In software, most of our time is spent manipulating data: read, transform and save it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |