11–20 of 140 posts
Earlier quoted context omitted.
It might not be common in typical software shops. I work in manufacturing and our database has multiple tables with hundreds of columns.
What's in them?
> But SQL schemas often look like this. Columns are nullable by default, and wide tables are common. Hard disagree. That database table was a waving red flag. I don't know enough/any rust so don't really understand the rest of the article but I have never in my life worked with a database table that had 700 columns. Or even 100.
It might not be common in typical software shops. I work in manufacturing and our database has multiple tables with hundreds of columns.
> But SQL schemas often look like this. Columns are nullable by default, and wide tables are common. Hard disagree. That database table was a waving red flag. I don't know enough/any rust so don't really understand the rest of the article but I have never in my life worked with a database table that had 700 columns. Or even 100.
So it sounds like helping customers with databases full of red flags is their bread and butter
> But SQL schemas often look like this. Columns are nullable by default, and wide tables are common. Hard disagree. That database table was a waving red flag. I don't know enough/any rust so don't really understand the rest of the article but I have never in my life worked with a database table that had 700 columns. Or even 100.
> But SQL schemas often look like this. Columns are nullable by default, and wide tables are common. Hard disagree. That database table was a waving red flag. I don't know enough/any rust so don't really understand the rest of the article but I have never in my life worked with a database table that had 700 columns. Or even 100.
https://jimmyhmiller.com/ugliest-beautiful-codebase
> But SQL schemas often look like this. Columns are nullable by default, and wide tables are common. Hard disagree. That database table was a waving red flag. I don't know enough/any rust so don't really understand the rest of the article but I have never in my life worked with a database table that had 700 columns. Or even 100.
> But SQL schemas often look like this. Columns are nullable by default, and wide tables are common. Hard disagree. That database table was a waving red flag. I don't know enough/any rust so don't really understand the rest of the article but I have never in my life worked with a database table that had 700 columns. Or even 100.
https://jimmyhmiller.com/ugliest-beautiful-codebase
https://www.postgresql.org/docs/current/storage-page-layout....
Earlier quoted context omitted.
It might not be common in typical software shops. I work in manufacturing and our database has multiple tables with hundreds of columns.
What's in them?