3 ms·
The 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 tho
by mrkeen 2y ago
The 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