[5.5] Add precision to dateTime and timestamp column types

[dschniepp]

Regarding to issues like #3506 and #11239 I would like to propose a grammar change which allows to set the precision of dateTime and timestamp fields.

• MySQL fully supported
• PostgreSQL fully supported
• SQLite has no date time
• MSSQL unfortunately I can't test it.

The maximum granularity of the fractional seconds depends on the RDMS.

[lucasmichot]

@param int $precision

[dschniepp]

Thank you, I missed that.

[taylorotwell]

None of these changes appear to actually let the user change the precision?

[dschniepp]

Sorry was my bad forgot to tweak the Blueprint Class. Now the user should be able to set the fractional seconds on the datetime and timestamp columns and also on the related functions like timestamps(), softDeletes() etc.

[fernandobandeira]

Actually on Sqlserver datetime(3) isn't supported, you can check the docs here

You can change that to use datetime2 it's available since sqlserver 2008, check the docs here wih this you'll be able to make it work since it support fractional seconds precision.

[dschniepp]

Is it necessary to support SQL Server versions below SQL Server 2008?

[dschniepp]

@taylorotwell is it necessary to support SQL Server versions below SQL Server 2008 if not I would change the column type to datetime2 like @fernandobandeira proposed.

[chkm8]

Hi, I just want to ask if this update about from datetime to datetime2 will be available on the next version or will be available in 5.4? Just wanted to know so that we could think a work around while waiting for the updates. Thanks.

[fernandobandeira]

@chkm8 I've pushed it to 5.5. On #18962

[chkm8]

Oh I see, thanks @fernandobandeira, will just wait until 5.5 is released next month.

[taylorotwell]

This breaks support for MySQL 5.5? Do we want to revert?

[dschniepp]

I wouldn't revert it but make the precision configurable like @fernandobandeira on #20262 (comment) already proposed.