default value not being set up

[stefanchiriac]

Hello,

If I set a default value doesn't seems to be considered when I run the migration

new Column('status', [
    'type'    => Column::TYPE_INTEGER,
    'notNull' => true,
    'size'    => 1,
    'default' => 0,
    'after'   => 'role_id'
]);

There are any plans to add support for bigint, tinyint, timestamp?

Thanks

[mattvb91]

I have just recently added pull request to the main phalcon repo because I needed to support blob types.

When I get time I will push bigint,tinyint and timestamp too. Hopefully they will make it into the 2.0.4 release.

[stefanchiriac]

@mattvb91 That sounds nice. Do you have problems with default value not being set up or is just me?

[mattvb91]

I seem to be having the same issue as you. Running v2.0.3 of the devtools.

I will look into this the same time as adding support for the new datatypes. I will update this issue if I have a branch you can test on.

[stefanchiriac]

any news about this issue?

[sergeyklay]

@stefanchiriac Curently we can use only Column::TYPE_BIGINTEGER because tinyint and timestamp isn't supported by Phalcon.

Can you explain please about "default values" related issue?

[stefanchiriac]

The problem is with mysql/mariadb when you have a default value on a column.

• if you generate a migration from a table, all default values are ignored and don't appear in your migration code.
• if you run a migration, the column default value is ignored and is not set in db. For running a migration and missing types a work around is defining everything on type

new Column('created_at', [
    'type' => "TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP",
]);

[sergeyklay]

@stefanchiriac
I've tried to fix this behaviour. Can you please check it now in 2.0.x branch? But note currently Phalcon does not support Columt::TYPE_TIMESTAMP

[stefanchiriac]

now seems to work to generate and apply a migration with default value, except when 'default' => 0. In this case the value is being ignored

[sergeyklay]

I'll try to deal with it

[sergeyklay]

@stefanchiriac I've tried to fix "default value" related issue. Can you please check it now in 2.0.x branch?

[stefanchiriac]

I did some debugging myself and seems like the problem comes from the framework.
I ran directly modifyColumn and createTable functions and no luck

self::$_connection->modifyColumn($tableName, $tableColumn->getSchemaName(), $tableColumn);
self::$_connection->createTable($tableName, $defaultSchema, $definition);

[sergeyklay]

@stefanchiriac I've fixed default value in Phalcon (2.0.x branch) phalcon/cphalcon#10849. Can you please build Phalcon from 2.0.x branch and check now?

[sergeyklay]

@stefanchiriac You can try now with Phalcon 2.0.x

new Column('created_at', [
    'type'    => Column::TYPE_TIMESTAMP,
    'notNull' => true,
    'default' => 'CURRENT_TIMESTAMP'
]);

[stefanchiriac]

all works fine now. Thanks

[sergeyklay]

👍