4 ms·
Having worked a lot with columnar data, I often have to tell the object oriented crowd that "It's the rows and columns, stupid!". (And that last sentence was a
by fifilura 2y ago
Having worked a lot with columnar data, I often have to tell the object oriented crowd that "It's the rows and columns, stupid!".
(And that last sentence was a paraphrase. They are far from stupid, just differently wired).
I think managers should be emboldened to do that too. They often work out their solutions in Excel. And then the developers turn those fine rows and columns into an object oriented soup.
- CalRobert 2y agoIt is indeed! But it fails when you need more dimensionality.
- mrkeen 2y agoThe problem is my rows typically don't have the same columns. A 'userCreated' row has 10 columns (for now), but a 'userDeleted' row overlaps on only two of those (let's say 'Datetime' and 'userId'). And userBanned brings in a new column 'reason' which isn't in the schema, so I have to store it in some catch-all json 'data' column which kills my db's size & performance. I persevere with the format, but always wish we were using the right tool for the job (nosql).
- 6510 2y agoAs I started out in a time when you had to coin your own format for everything I passionately hate it when the data has to facilitate to the tool. I'm no db wizard so I feel terrible using the json cell unsure about the level of sin involved. I also adopted comma separated fields. Don't tell anyone