Title: Database Constraints
Last modified: November 9, 2018

---

# Database Constraints

 *  Resolved [borntohula](https://wordpress.org/support/users/borntohula/)
 * (@borntohula)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/database-constraints/)
 * Hi,
 * We migrated on the 27th October to Flywheel. We’ve just noticed that in the SQL
   Database CONSTRAINTS hadn’t been updated. So the tables were referencing the 
   old table prefixes, rather than the new Flywheel prefixes. The plugin Bookly 
   uses constraints.
 * We resolved the issue manually, but thought it’s worth highlighting to you.
 * Thanks

The topic ‘Database Constraints’ is closed to new replies.

 * ![](https://ps.w.org/migrate-guru/assets/icon-256x256.png?rev=3411815)
 * [Migrate Guru – Site Migration & Cloning](https://wordpress.org/plugins/migrate-guru/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/migrate-guru/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/migrate-guru/)
 * [Active Topics](https://wordpress.org/support/plugin/migrate-guru/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/migrate-guru/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/migrate-guru/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [borntohula](https://wordpress.org/support/users/borntohula/)
 * Last activity: [7 years, 7 months ago](https://wordpress.org/support/topic/database-constraints/)
 * Status: resolved