SQLite Errors on running .migrate() about evolve HOT 7 CLOSED

Well, I reproduced partially your issue. I saw in the output window the SQLite error you mentioned.
But not 3 times for each migration scripts. Only 3 times by migration. Do you run Evolve.Migrate() multiples times ?

from evolve.

Apologies, I must've had something else going on to have it happen multiple times as I can't reproduce that part now. It is only the 3 for the whole migration.

from evolve.

That method was my best guess as to the cause of it. It was the only place I saw the "SHOW" sql query being used. Just seems weird if I'm providing the Driver when instantiating the class, shouldn't that be an indication?

As I mentioned, it definitely doesn't impact the performance of the framework (which is really fantastic by the way!), so if this isn't something that would be a simple fix feel free to close it :)

from evolve.

These messages are due to the method I use to determine the database you use (SQL Server, SQLite, PostgreSQL ...)

I will try to use an another strategy in a future version, but honestly, because the migrations work fine
it is not in my top priority list.

And yes, afterwards it's seems a bit awkward to guess what database you use that way. 😔

There had to be a reason.... I hope.

from evolve.

Totally fair! Thank you for the quick responses :)

from evolve.

@Andrewwelton I finally remember why I use this method to detect what type of DBMS is used. That's because Evolve can run in "App-Mode" (you instanciate the class Evolve in your code) and this way can be started with a DbConnection object in the constructor, without any driver specified.

I don't know any other method to determine wich kind of database is used with only a IDbConnection

Are you ? 😉

from evolve.

Yeah that totally makes sense, I'm using the "App-Mode" myself :)

My thought was that if I instantiate the Evolve object in app like this:
var evolve = new Evolve.Evolve(connection, Console.WriteLine) { Driver = "sqlite" };

I've provided what type of connection the IDbConnection is when I instantiated the Evolve object, so doing the extra work to try and figure it out seemed unnecessary.

from evolve.