3 ms·
Nope. That's a problem of your code, not a schema on the database. You could have those functions return something optional, where a None is returned when the d
by karmakurtisaani 4y ago
Nope. That's a problem of your code, not a schema on the database. You could have those functions return something optional, where a None is returned when the data doesn't conform to the assumed schema, and you're safe again. You could have cats and dogs and cars in your employee database and not run into problems.
In fact, this is how you have to work when you're dealing with large amounts of unstructured data.
- stouset 4y ago> You could have those functions return something optional, where a None is returned when the data doesn't conform to the assumed schema Again, you have a schema. It's just invisible and implicit, and you have no tools to manage, enforce, or deal with it.
- karmakurtisaani 4y agoIf you define it like that, what's the point of the concept of schema at all? When I say no schema, I mean the user has no control over what's in the data. They can query for employee id's, pet names, birthdays, etc., and get back meaningful data or just Nones. Thinking about a schema this way is useful.