jsanders

Musings upon the JSON OBJECT: How far CAN you go?

Discussion created by jsanders on Nov 25, 2018

... and how far SHOULD you go?

 

 

Theoretically, couldn't ALL the data in my my entire database be represented in one massive JSON object of JSON objects in a text or container field?  I'm at sureness factor 987 that this is a bad idea, for many reasons.  One that pops to mind is the complexity of calculations and scripting that would be required to report and display sub sets of data for individual jobs or groups of jobs.

 

I'm pretty comfortable that stowing all your data is one ginormous JSON object is a bad idea, but stowing SOME data or some types of data as JSON objects makes perfect sense.  Where is the sweet spot?  What questions do we ask to discover the sweet spot?

 

If I have Tables:

 

CUSTOMERS

VENDORS

EMPLOYEES

CONTACTS

LOCATIONS

JOBS

SERVICES

INVOICES

LINEITEMS

INSURANCE CERTIFICATES

 

Does it make sense to the the CUSTOMERS table consist of a single record with a single container or text field with a big ass JSON object it?

 

Is it a horrible idea for each of these tables to be  single field, single record JSON monsters?  I'm pretty sure it is but my sureness factor is only 437...  Could this actually be a great idea? Fire when ready?

Outcomes