An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how entities relate to each other within a system. In terms of a database management system, an entity is a table. So by showing relationships among tables, the ER diagram represents the complete logical structure of a database.
Our readers are already familiar with Louis, who not only uses DBeaver for his work but also uses it for his favorite hobby. He has a website where he regularly publishes information about films, and he stores all the necessary data in a database. Louis realized one day that it was not only he but also his readers who were interested in information about popular TV series.
DBeaver supports a large number of databases with different purposes. Relational databases remain the most common databases our users constantly work with, and our app offers a wide range of features for working with the data stored in them. For your convenience, we have added the ability to visualize data to our PRO versions as one more way to work with data.
In our previous article, we talked about transactions and how they work in DBeaver. When you are in the development and testing phase of your project, there is usually no need to keep track of transactions. But if we are talking about a production system, we need stricter control over reading and editing data. Therefore, DBeaver has Connection types that allow you to track transactions only when you need to.
If you work with databases, it is highly likely that you have already used transactions even if you weren’t aware of it. Let’s talk about what transactions are and how they work in DBeaver.
Our hero Louis, who you would have read about in one of our previous articles, has a new hobby. As he is quite fond of going to the cinema, he has created his own website with information about movies. Louis stores movie titles and descriptions, cast lists, and other information in a database and updates it regularly. And with DBeaver, he can easily keep his site up-to-date.
When you just start working with DBeaver and create the first few connections to different databases, you will have no problems with organizing your navigation tree. But what if you are working on multiple projects with dozens of scripts and diagrams? In this case, your navigation tree starts looking messy. To organize it, you can use Projects in DBeaver.
Let’s take a look at a small company that manufactures and sells merch all over the world using its own online shop. The boss asked his assistant Louis to reward regular customers by sending them gifts. To get a list of the mailing addresses, he needs to select the desired group of customers.
How can he do all of this with DBeaver?
Today, databases do not store only strings and numbers, as it used to be. You can use your database for different data types, including images, spatial data, and even data structures such as JSON. If the text value is easy to edit right in the table cell, working with more complex data types can be difficult. Today we will talk about how DBeaver’s Value Panel solves this problem.
