All Blog Posts  |  Next Post  |  Previous Post

My Top 10 Aurelius Features - #7 Schema Update


Tuesday, January 3, 2017

When creating a database-based application, one of the tasks I always considered boring was to create the database structure, table, fields, foreign keys. Even using a tool to generate a SQL would require me to create a table, add columns, column types, foreign keys, etc.

That's why I consider the ability to automatically create and update the database schema to be the #7 feature of My Top 10 Aurelius Features. It's simply something I don't need to care about anymore.

Updating the database is as easy as doing this:
That simple command will check the existing schema in the database and create the missing objects needed to persist all the objects you are dealing with: new tables, columns, foreign keys.

Note that I'm talking about updating, not creating the database. That makes application prototyping and development really fast. Create the database, change your application, add a new table, update the database, and it goes on.

Even though updating the database is as simple as using one line of code, Aurelius provides advanced features for the database update process, like validation. With a code like the following, you can check the differences between the schema of the existing database, and what is needed in the schema to hold the current entity model you have. It shows you the differences without requiring you to actually execute the SQL statements:
procedure TForm1.ValidateMyDatabaseSchema;
  DBManager: TDatabaseManager;
  Action: TSchemaAction;
  Warning: TSchemaWarning;
  Error: TSchemaError;
  DBManager := TDatabaseManager.Create(Connection);

    { Show SQL statements }
    for Statement in DBManager.SQLStatements do

    { Show validation results }

    mmValidation.Lines.Add('----- Actions -----');
    for Action in DBManager.Actions do
      mmValidation.Lines.Add(Format('%s -> %s', [Action.ClassName, Action.Text]));

    mmValidation.Lines.Add('----- Warnings -----');
    for Warning in DBManager.Warnings do
      mmValidation.Lines.Add(Format('%s: %s', [Warning.ClassName, Warning.Text]));

    mmValidation.Lines.Add('----- Errors -----');
    for Error in DBManager.Errors do
      mmValidation.Lines.Add(Format('%s: %s', [Error.ClassName, Error.Text]));
Please watch the video (closed captions available!) to see how schema update and validate in action. As usual, don't forget to subscribe to our YouTube channel and receive notifications about upcoming videos!

Wagner Landgraf


This blog post has received 2 comments.

1. Wednesday, January 4, 2017 at 5:56:13 PM

It would be great if you uploaded your programs from these great webcasts so we can have them offline.
This is an absolutely great series, exactly what is needed to get started productively with Aurelius! Thank you!

Neal Campbell

2. Monday, January 9, 2017 at 11:38:23 AM

Hi Neal, thank you for the compliments. If you mean the source code of projects used in the series, problem is that there isn''t much, most is just code snippets and use of tools. But please contact us directly through e-mail if you need more info about a specific video.

Wagner R. Landgraf

Add a new comment

You will receive a confirmation mail with a link to validate your comment, please use a valid email address.
All fields are required.

All Blog Posts  |  Next Post  |  Previous Post