A new topic, 'warning of losing primary key/autoincrement for mysql', has been
made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=989.new#new
The text of the topic is shown below:
Hi everyone,
I got the following warning.
WARNING 11-1-26 afternoon 8:52:liquibase: modifyDataType will lose primary
key/autoincrement/not null settings for mysql. Use <sql> and re-specify all
configuration if this is the case
Does this mean if i use modifyDataType statement on a primary
key/autoincrement, it will lose autoincrement and not null settings? Could you
explain it?
Cheers,
Cheng Wei
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Liquibase-user mailing list
Liquibase-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/liquibase-user
