DataGrip 2017.1.4 is Out
Hi! We have a small update for DataGrip 2017.1, with a few fixes that will be important for some of you:
DBE-4570 – Trigger editor works properly now.
DBE-4282 – Fixed bug with wrong column order in MySQL.
DBE-2338 – Introspection in Sybase became faster. Thanks to Ian Moult for offering a better query to run!
Stay tuned!
DataGrip team.
fitrah says:
May 17, 20171. How to display the schedule MySql in Data Grip?
2. How create field ON Update in MySql?
3. Why copy data error “1: Data truncation: Out of range value for column ‘msisdn’ at row 1”. MSISDN (BIGINT) and data length 13 example 6281234556671
Thank you
Maksim Sobolevskiy says:
May 24, 20171. There is no UI for this
2. Do you mean a trigger?
3. It’s a problem with your data, please describe in details and attach the screenshot.
wuling says:
May 31, 2017ON UPDATE CURRENT_TIMESTAMP unable to display
Maksim Sobolevskiy says:
May 31, 2017If it shows null instead of zeroes (if it wasn’t updated at all), please configure it like it’s shown in our FAQ: https://confluence.jetbrains.com/display/DBE/FAQ
DS properties → Advanced → zeroDateTimeBahaviour
wuling says:
June 1, 2017MySQL Table structure in the DDL statement ON UPDATE CURRENT_TIMESTAMP is not displayed.
sql:`modify_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT ‘modify_time’;
but displayed:`modify_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘modify_time’;
Thank you
Maksim Sobolevskiy says:
June 13, 2019What are your versions of DataGrip and MySQL? Also, a screenshot of the data source properties will be useful: Options Tab.
Joe says:
May 17, 2017So where was the announcement (and release notes) for 2017.1.3?
Maksim Sobolevskiy says:
May 24, 2017There were just super-minor fixes: https://twitter.com/0xdbe/status/859706307074502657
freya.fu.z says:
June 13, 2019same with wuling.
ON UPDATE CURRENT_TIMESTAMP unable to display