You have to do $table->dropUnique(‘users_email_unique’); To drop an index you must specify the index’s name. Laravel assigns a reasonable name to the indexes by default. Simply concatenate the table name, the names of the column in the index, and the index type.
Ah, figured this out accidentally. I had to remove public MasterEntities() : base(“name=MyApplicationEntities”) // ^^^^^ { } to public MasterEntities() : base(“MyApplicationEntities”) { } EF 4.3 does not like connection string being called name=xxxxx
for fun, you can also manipulate these in the console by making a model class for them… class SchemaMigration < ActiveRecord::Base; self.primary_key = :version; end then you can do SchemaMigration.all, SchemaMigration.last.delete, etc. Really just a substitute for using SQL, and it is very rare that you would need to mess around at this low level… … Read more
You can squash it with the previous migration, sure. Or if you don’t want to output those migrations at all, you can override the makemigrations and migrate command by putting this in management/commands/makemigrations.py in your app: from django.core.management.commands.makemigrations import Command from django.db import models IGNORED_ATTRS = [‘verbose_name’, ‘help_text’, ‘choices’] original_deconstruct = models.Field.deconstruct def new_deconstruct(self): name, … Read more
Laravel development is about freedom. So, if you need to seed your production database and think DatabaseSeeder is the best place to do so, why not? Okay, seeder is mainly to be used with test data, but you’ll see some folks using it as you are. I see this important kind of seed as part … Read more
According the Polls tutorial: python manage.py makemigrations <app>: Create the migrations (generate the SQL commands). python manage.py migrate: Run the migrations (execute the SQL commands).
Drop foreign key first. Thanks to Razor for this tip $table->dropForeign(‘answers_user_id_foreign’); $table->foreign(‘user_id’) ->references(‘id’)->on(‘users’) ->onDelete(‘cascade’);
I’m guessing your build of L5 is fairly old, as they disabled creating migrations alongside the model creation. Try running the ff: php artisan make:model Settings –migration
You need to add your table to your implementation of the DbContext class, e.g. public class MyDatabaseEntities : DbContext { public virtual DbSet<MyTable> MyTable { get; set; } }
You can use MySQL Workbench which provides a way to quickly migrate data and applications from Microsoft SQL Server to MySQL employing less time and effort. This tool has a lot of cool features like: Database migrations – enables migrations from Microsoft SQL Server, Sybase ASE and PostgreSQL. Migration project management – allows migrations to … Read more