me and my boss plan to make a new feature to our system.

i model the database tables

he says that there are too many tables

i say its atomic and acid

he says to put all the columns in a single table

where I work there are some tables with 200 columns... I always freakout whenever I have to deal with them...

Are these tables normalized? Problems show up down the road and then the very expensive rewrite. Very expensive. Seen it many times. Although profitable for the dev that rewrites it.

@Jumpshot44 i say this shit doesnt scale, this shit gonna fuck up the servers, but he doesnt care

@g-m-f the dumbass said he would put all the data in a single table if he could lol

Try working with a large ERP system, there are hundreds of tables. Each table has at least 50 rows per standard. It's so bad that some of the tables don't even have primary keys or correct indexes. Don't bother trying to fix it, you don't know what you'll break.

@distinct I think I know the feeling... Imagine a DW with ca. 20TB of SAS tables. I've managed to write a meta query to initialize a value date, that actually works well. Turns out that the meta hasn't been thoroughly updated since 2006. --> the vast majority of the flows and jobs exits with error...

@distinct as a matter of fact, we got 85 tables here, NONE of them have keys, so data are often duplicated, and many to many tables doesnt work well cuz they cant lock the keys. its the biggest mess of the world lol

um still here cuz i receive a fair wage

@sn4i1 I meant 50 columns rather rows, but I'm sure everyone here knew what I meant. Sounds like your situation is just as bad if not worse. =S I do not envy you.

@slim it's the only reason devs put up with this shit. =P

Why not write to a tab-delimited file as a "database"?

@m001 he says he is creating a whole new SQL paradigm with these single table databases lol...

@g-m-f awesome comment

@slim you fix this mess and I will ask devRant to +100 you. Your boss is out of control.