If you use migrations, you could use something like this:

public class InitialMigration : MigrationBase
{
    public InitialMigration(IMigrationContext context) : base(context)
    {

    }

    public override void Migrate()
    {
        if (!this.TableExists("BlogComments"))
        {
            this.Create.Table<BlogComment>().Do();
        }
    }
}

Stephan has write a blog about migrations in V8 - https://www.zpqrtbnk.net/posts/migrations-in-v8

And if I don't want to run this from a migration (since it needs to run on every app start), could I also execute that code from a component? https://creativewebspecialist.co.uk/2018/06/15/umbraco-v8-bye-bye-applicationeventhandler-hello-umbraco-components/

Tim,
Any reason you need to run SQL everytime the app boots?

As everyone has mentioned, using migrations is the way to go for this.

With migrations it will save you this work, if an envionment such as local to development or development to live, has not run a migration (the current latest state of a migration is stored)

So if the Live site does not have migration-c but has migration-a in its DB it will go through migrations migration-b & migration-c

So migrations is the way to deal with SQL/Table stuff. Look at V8 core and how many migrations we have just for V8.0.0 https://github.com/umbraco/Umbraco-CMS/tree/temp8/src/Umbraco.Core/Migrations/Upgrade/V80_0

And take a look at what we do again in V8 core to ensure we go through all the steps/migrations in a specific order https://github.com/umbraco/Umbraco-CMS/blob/temp8/src/Umbraco.Core/Migrations/Upgrade/UmbracoPlan.cs

Hope this helps.

Cheers,
Warren

But if you need or want to use SQL/NPoco (The PetaPoco replacement) you could use something like this.

Note the scope.complete() without it, the transaction/SQL will not be applied.

using (var scope = Current.ScopeProvider.CreateScope())
{
    var sql = scope.SqlContext.Sql()
        .Select<Record>(x=>x.Form)
        .From<Record>()
        .Where<Record>(x => x.UniqueId == recordId);

    var formId = scope.Database.ExecuteScalar<Guid>(sql);

    scope.Complete();

    return GetForm(formId);
}

Hi Warren, thanks for the details, well I need it to run more then once since I'm building up types on the fly based user input.... , is there a way I can force execute a migration? Or in your second example how would you create a table based on a type?

THanks, got an example of using the Scope approach and combining it with

if (!TableInfo.FromPoco(typeof(BlogComment)).TableName)
{
    Create.Table<BlogComment>().Do();
}

Since I don't see any create table stuff on there

Nope not yet Bo, @Warren any further ideas?

is working on a reply...