The long-awaitedgeneration of SQL migration scriptsis now a part of Vertabelo ! You can use these scripts toeasily move from one database model version to another. Read this article to learn more.What are SQL Migration Scripts?An SQL migration script is a script that alters an existing database structure: it can add or drop a table, rename columns, or change column types. A migration script can change a given database from one schema version to another – hence its name. It
Vertabelo has a great new feature: a model documentation auto-generator. You can now create and export documentation for your current model with just a few clicks. Vertabelo has a great new feature: a model documentation auto-generator. You can now create and export documentation for your current model with just a few clicks.Think of how a complex model looks: multiple tables and tens or hundreds of columns where you can easily get lost. In a situation like this, you could really do with some well-organized documentation that lists all the tables, references, columns and other parts of your model in a structured way. You could of course write the descriptions yourself, but that’s time-consuming and open to mistakes and omissions.
The XML file format for Vertabelo has changed to version 2.3. Read this article to find out what is new. Vertabelo keeps its models in XML format; if you need, you can download the files and extract information from them. Previously, we used XML version 2.1, as discussed in this article . We’ve switched to XML 2.3, and a couple of changes took place. These changesmake no difference for most Vertabelo users
jOOQ is a Java Object-Relational Mapper that lets you build type safe SQL queries through its fluent API. Using built-in Vertabelo support we can generate sufficient code from the previously designed model. Generated Java classes correspond to database tables, records, etc. This time, we automate this process by using Gradle build system.There are two ways to generate ready to use Java classes with Vertabelo : Generate jOOQ classes via Vertabelo XML
Various data modeling tools allow modelers to define relationships in a data-model as identifying or non-identifying. We can define a relationship as identifying or non-identifying in Vertabelo as well. This article will explain the way to do so.IntroductionBefore moving ahead with the article, I’d like to explain whatidentifyingornon-identifyingmean.Let’s take a real time example of a book storing system. In the system, a book belongs to an owner, and an owner can own multiple books. But the book can also exist without the owner and it can change the owner. Thus the relationship between a book and an owner is a non-identifying relationship.
jOOQ provides an easy way to automate the process of generating the java classes that represent database tables, records, etc. via thejooq-codegen-mavenplugin. This time we let Maven worry about downloading the required JAR files and generating Java code that lets you build typesafe SQL queries through jOOQ’s fluent API.There are two ways to generate ready to use Java classes with Maven and Vertabelo: Generate jOOQ classes via Vertabelo XML
jOOQ and Vertabelo perfectly complement each other in the application development lifecycle. With Vertabelo you can easily design a database structure that saves you from writing DDL code manually, while jOOQ handles the generation of Java classes corresponding to database tables, and allows to construct SQL queries through its fluent API.The integration of Vertabelo and jOOQ has been the subject of several articles published on our blog. Unfortunately, all of them, including
Even though Vertabelo doesn’t provide a direct conversion of a data model from one database engine to another, this can be easily done in a few simple steps.The user’s questionWe’ve been developing a web application for a while. Initially, we wanted to use MySQL for our database but finally we decided to choose Postgres. Unfortunately, the entire data model was created for MySQL. How can we quickly migrate it to the new database type? Is there a simple way to do this in Vertabelo?
Tell us what you want!If you have your own ideas for new features or you think that something could be improved in our application, do not hesitate to share your opinion. Send your suggestions to us via our Support Service . There, you can upvote or downvote new feature requests placed by other users. That way, you can have a significant impact on the development of our application. Go to Vertabelo’s Support Service »
Flask is a web microframework for Python. It uses Flask-SQLAlchemy for object relational mapping. It is a Flask wrapper for SQLAlchemy – a powerful relational database framework that offers a high level ORM and low level access to a database’s native SQL functionality.For each database table, SQLAlchemy uses a regular Python class with attributes that match the columns of a corresponding database table. The database instance from Flask-SQLAlchemy provides a base class for models called
Our users sometimes say to us: “Vertabelo is awesome but… how can I add the data?” Oh, come on! Vertabelo is not a database engine or a database administration tool. At least not at the moment. For now, Vertabelo is intended mainly to design database models. This doesn’t mean that we don’t care about what you can do next with models created in our application. Of course, we do! That’s why we provide our users with some useful tools on
If you’ve ever had to design a database model with hundreds of tables, views and references, you know very well how difficult is to make such huge diagram readable and comprehensible. One of the possible solutions is to use some colors to distinguish different groups of tables or subject areas. See how Vertabelo allows you to do this quick and easy.To illustrate how you can color your entity relationship diagram to increase its readability, we will use a sample uncolored database model for a simple online store:
Most relational databases allow you to define comments for their tables, columns, views, and so on. These additional pieces of information are called databasemeta dataordata dictionary. Meta data may be useful for developers or other database users. Meta data allow the development team to understand what various tables or columns are for without having to ask database designer what their intentions were.Generating meta data in SQL scripts is one of the most often requested Vertabelo features and it’s finally here. Here’s how you can take advantage of the feature.
If you use Propel, you can now generate a Propel schema file from a database model created in Vertabelo. Propel is a popular ORM (Object-Relational Mapping) library for PHP. In Propel, the datamodel structure is described by a special schema XML file. From this schema Propel generates PHP object model classes which Propel uses to represent rows in your tables. VertabeloPropel is a PHP script which converts a Vertabelo XML file into Propel’s schema.xml file.
We hadn’t planned on adding a feature to print diagrams. Our original idea was that Vertabelo would supersede paper diagrams. Nevertheless, some of our users pointed out that they rely heavily on printouts ( Export to PDF topic). So, I’d like to announce a new feature called “Export to PDF” also known as “Printing.”Note that exporting a database model to a PDF file is available for Premium and Team account plans only (see the comparison of the plans’ features in our
Vertabelo internally stores your model in an XML format. You can download the XML file and use it to extract some information by using a script. Let’s take a look at the structure of this XML file.Here is the XSD file and an example of the XML file for the above sample database model created in Vertabelo .The root element of the document is the DatabaseModel element with the VersionId attribute. As of today, the current version is 2.1.