Updated syncdb -> migrate in tests.

class FixtureLoadingTests(DumpDataAssertMixin, TestCase):

    def test_initial_data(self):

        # syncdb introduces 1 initial data object from initial_data.json.

        # migrate introduces 1 initial data object from initial_data.json.

        self.assertQuerysetEqual(Book.objects.all(), [

            '<Book: Achieving self-awareness of Python programs>'

        ])

    available_apps = ['fixtures_model_package']

    def test_syncdb(self):

    def test_migrate(self):

        with transaction.atomic():

            Book.objects.all().delete()

            management.call_command(

                'syncdb',

                'migrate',

                verbosity=0,

                load_initial_data=False

            )

class FixtureTestCase(TestCase):

    def test_initial_data(self):

        "Fixtures can load initial data into models defined in packages"

        # syncdb introduces 1 initial data object from initial_data.json

        # migrate introduces 1 initial data object from initial_data.json

        self.assertQuerysetEqual(

            Book.objects.all(), [

                'Achieving self-awareness of Python programs'

    def test_custom_sql(self):

        """

        Simulate the custom SQL loading by syncdb.

        Simulate the custom SQL loading by migrate.

        """

        connection = connections[DEFAULT_DB_ALIAS]

        custom_sql = custom_sql_for_model(Simple, no_style(), connection)

# Regression for #11226 -- A model with the same name that another one to

# which it has a m2m relation. This shouldn't cause a name clash between

# the automatically created m2m intermediary table FK field names when

# running syncdb

# running migrate

class User(models.Model):

    name = models.CharField(max_length=30)

    friends = models.ManyToManyField(auth.User)