Is there away to have parts of a migration file only work with a
specific database. For example I am inserting some data into a table
execute "INSERT INTO demo_lists(position, name, updated_at,
created_at) VALUES (1, 1, ‘scott’, CURDATE(), CURDATE());"
Of course the curdate() function may only be available on mysql. So can
we some how determine which database type Migrations is working on? I
would assume there’s away since my Migrations class extends
What’s an Intel chip doing in a Mac? A whole lor more that it’s ever
done in a PC.