We have subsections for the columns that make up the table, the various keys, including the primary key for the table or the foreign keys that are related to other tables in the database. That's exactly what we see on this Properties tab. Now, if you've ever created a database table, then you know that you need to define each column of the table, and the types of data that they'll contain, as well as other configuration parameters. Okay, let's go back up here to the top and switch back to the Properties tab. Now, at the very bottom of the editor window, you'll find another dynamic toolbar that contains items for working with each of the different object's components. It'll probably be fixed in an upcoming DBeaver update. So if you see that, don't really worry about it. It's just a strange visual quirk with the interface. Hovering your mouse over the text will flip it right side up. The text will sometime appear upside down for some reason. Now, at the time of this recording, I've noticed a visual bug that sometimes occurs with this object path. In this case, we're exploring the sample database and in the inside of the tables folder, we'll find the employees table. #DBEAVER REVIEW HOW TO#This displays the breadcrumb trail of how to get to the specific object. On the far right, we have a database object path. One for the data that the table contains and one for the ER or the entity relationship diagram that tells me how this data table corresponds to the other tables within the database. Below that we have a set of different tabs that correspond to the different types of components that make up our employee table. So here at the top, I have the tab name Employee that corresponds to the table object that we just opened up. This is where you're going to go to work with all of your different database objects. I'll double click on the employee table and it opens up in a new editor tab. To view the content of each of these database objects, just double click on its name. For instance, you wouldn't expect to find indexes, relationship keys and store procedures when connecting to a flat-file CSV simply because those aren't a feature of the CSV file format. It just depends on what kinds of features the data platform supports and how they're configured. Depending on the type of database resource that you're connected to, you'll find different sets of these components. The database navigator tree is very similar to the types of interfaces that you would find in SQL Server Management Studio, PostgreSQL's pgAdmin, Microsoft Access or really any other database management application. They have columns, primary and foreign keys, indexes, references and triggers. Digging further, each of these tables is made up of the typical components. And it includes data on their album inventory, sales history, and employees. This database is made up of tables that support a music store. Now, you can expand any of these folders to see those individual components. We have group folders for the different tables that are within the database, the view objects, indexes and so on. And when you expand it, you'll find that it's made up of a number of different components, just like most relational databases. The DBeaver sample database is a great place to start when you're getting to know how the application works.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |