Not a bug, but a proposal for an upgrade/feature on migrations

[awesomeguy3]

As I said in the title, this is not a bug, but a proposal (didn't know where to write this that would be seen.

Now, on my project I have a big database (not in terms of data but in terms of tables and columns in those tables), and I also have a lot of indexes.
I noticed today that I need to write in a migration class
$this->createIndex('name', 'table', ['columns'])
after creating a new table, what I'm thinking should be a good idea is to add a possibility for method chaining on "createTable" function where I wouldn't need to enter table name for every index.
Or perhaps another parameter in createTable function that would easily let me add indexes in one place.

[samdark]

How would the syntax look like?

[awesomeguy3]

Maybe something like

$this->createTable('tableName', [
    'id' => $this->primaryKey(),
    'column' => $this->string()
], 'some options', [
    'index1' => ['column1', 'column2'],
    'index2' => ['column3']
]);

OR

$this->createTable('tableName', [
    'id' => $this->primaryKey(),
    'column' => $this->string()
], 'some options')->index('index1', ['column1', 'column2'])->index('index2', 'column3');

And forgive me for not knowing how to format code better in Markdown.

[samdark]

Formatting is easy: https://guides.github.com/features/mastering-markdown/

[samdark]

Second options looks interesting...

[awesomeguy3]

I personally like first option better, but whatever you make is okay with me.

[kjusupov]

$this->createTable('tableName', 
        [
            'id' => $this->primaryKey(),
            'column' => $this->string()
        ]
)->createIndex(
        ['index_one', 'column1'],
        ['index_two', ['column1', 'column2']],
        ['index_three', ['column1', 'column2']],
)->createForeignKey(
        ['FK_name_one', 'column1', 'table1', 'column'],
        ['FK_name_two', 'column2', 'table2', 'column']
);

[Sarke]

How about something like this?

$this->createTable('tableName', [
    'id' => $this->primaryKey(),
    'column' => $this->string()->index(),
]);

Not sure if that would work with ColumnSchemaBuilder, and if not maybe something like this?

$this->createTable('tableName', [
    'id' => $this->primaryKey(),
    'column' => [$this->string(), 'index' => true],
]);

If it's just true then create an index for that one column with that name (I think this is the most common). otherwise a string with the name of the index.

A solution like @kjusupov would be required for more complex indices, but sounds like it would require something like a TableSchemaBuilder perhaps?

[rob006]

I'm for

$this->createTable('tableName', [
    'id' => $this->primaryKey(),
    'name' => $this->string()->index('indexName'),
    'topic_id' => $this->integer()->foreignKey('indexName', 'referencedTable', 'referencedColumn'),
]);

[awesomeguy3]

Great ideas, but what about complex indexes?

[rob006]

We already have createIndex() for complex indexes.

[michaelarnauts]

I'm in favor for chaining like @kjusupov exampled. This fits with the current way of constructing the migrations.

[rob006]

I'm in favor for chaining like @kjusupov exampled. This fits with the current way of constructing the migrations.

This syntax does not give you any real benefits, it creates only another way to do the same thig (which usually decrease readability).

[awesomeguy3]

I'm with @rob006 on this one, his example is quite good.

[santilin]

The syntax proposed by @rob006 allows sqlite3 to create foreign keys at the same time that the table, which is the only way to add a foreign key in sqlite3 so far, although I am working on adding that feature to yii2/sqlite3: #15007

[omzy]

@kjusupov

$this->createTable('tableName', 
        [
            'id' => $this->primaryKey(),
            'column' => $this->string()
        ]
)->createIndex(
        ['index_one', 'column1'],
        ['index_two', ['column1', 'column2']],
        ['index_three', ['column1', 'column2']],
)->createForeignKey(
        ['FK_name_one', 'column1', 'table1', 'column'],
        ['FK_name_two', 'column2', 'table2', 'column']
);

The only issue I have with this approach is that you'd need to remember the order of parameters for createForeignKey() etc (unless you use an IDE that can tell you the parameters).

A better approach I think would be to make it mandatory to include the keys in the array, e.g:

$this->createForeignKey([
    'column' => 'user_id',
    'references' => 'id',
    'on' => 'user',
    'onDelete' => 'cascade',
]);

Note in this example, I didn't include the FK name - this should be optional and auto-generated (based on column and table name) if it isn't included.