Hi everybody
It turns out that current_timestamp(6) and now(6) give same value.
My point is :
Why does "Schema Compare" show a difference that is not corrected while synchronizing ?
Is there an option I should set to change this behaviour ?
Thanks
Regards
BD
Search found 2 matches
- Tue 28 Jun 2022 21:17
- Forum: dbForge for MySQL
- Topic: Schema Compare - changing default datetime column value
- Replies: 2
- Views: 8603
- Mon 27 Jun 2022 21:36
- Forum: dbForge for MySQL
- Topic: Schema Compare - changing default datetime column value
- Replies: 2
- Views: 8603
Schema Compare - changing default datetime column value
Hi
Context :
I get an issue while synchronizing my table column from source :
to update target :
Difference is shown after comparison, but synchronization won't change anything.
Is this a known bug or am I missing something.
Context :
- Windows 11
- dbForge Schema Compare for MySQL Professional Edition 5.0.622
I get an issue while synchronizing my table column from source :
Code: Select all
$DteCre DATETIME(6) NOT NULL DEFAULT (CURRENT_TIMESTAMP(6)) COMMENT 'Date de création de l enregistrement.',Code: Select all
$DteCre DATETIME(6) NOT NULL DEFAULT (now(6)) COMMENT 'Date de création de l enregistrement.',Is this a known bug or am I missing something.