Recently in my Grails project I mentioned a domain field as unique in constraints. So the table automatically created also had the same constraint, but as the requirement changed the field was not supposed to be unique. Now we need to remove that constraint from the database table as well. The trick in MySQL is that it stores the unique constraint fields as an index and not like other constraints so we cannot do the drop constraint for a unique constraint. The simple solution for this is to drop the index like this:<\/p>\n
alter table person drop index address<\/pre>\nIt worked.
\n<\/p>\n
Hope it helps
\nUday Pratap Singh<\/a>
\nuday@intelligrape.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Recently in my Grails project I mentioned a domain field as unique in constraints. So the table automatically created also had the same constraint, but as the requirement changed the field was not supposed to be unique. Now we need to remove that constraint from the database table as well. The trick in MySQL is […]<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[1],"tags":[301,302,300,303],"class_list":["post-1164","post","type-post","status-publish","format-standard","hentry","category-technology","tag-drop-constraint","tag-drop-constraint-in-mysql","tag-drop-unique-constraint","tag-drop-unique-constraint-in-mysql"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t