Please allow ads on our site
LoginMysql : Custom validation for 'JSON' data
General Tech Bugs & Fixes 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Similar Forum
Explore Other Libraries
Online Exams
Question Bank
Career News
Feeds
Full Forms
Dictionary
Interview Question
Gigs
Quotes
Lyrics
Videos
Courses
Blogs
Tutorials
Forum
Educators
Corporates
Tools
manpreet![Tuteehub forum best answer]()
Best Answer
3 years ago
From version 5.7, mysql had started to support 'Json' as the first class data-type construct (within a given mysql column). Seems it only validates the json structure, and no custom (restricted json structure) validation can be enforced for the 'Json' schema.
Any specific rationale for mysql not supporting such stricter constraints (they just seem to do an 'uber json validation' without any further enforcements) ? The same does not allow the user to have a fixed Json schema at the backend.
Other stores (MongoDB) have started to enforce such constraints. What could be the reason mysql doesn't supports the same.
Would like to understand the reason the for this current restriction in mysql.