Gregory's Server@lettosprey
It's OK, we've got JSON now.
Oh, JSON column data format? We're fscked.
|
5 comments
@M0KHR @lettosprey JSON columns are actually very good. For storing JSON. Which you sometimes may want to do! And sometimes it's a good idea! Postgres also does it very efficiently and can even index the hell out of it! Sure, it's not normal, but as long as we don't make non-normal the new normal...  Devs are terribly afraid of schema changes, because 20 years ago they were painful. JSON column data format + virtual columns + indexes on virtual columns allow you to do schema evolution in a way that does not scare devs to death. It's okay.  @M0KHR @lettosprey We got JSON Schema, aka, reinventing XML but with worse syntax and less standardization. Go team! |
@M0KHR At least, we still have a relational database to query.
We are not replacing mysql with json :O