Its official, the biggest bullshit table so far here at work

I wonder how it's named...

Lets see some data!

Column one: "Is"
Column two: "this"
Column three: "the"
Column four: "real"
Column five: "life"

What?? Relational model?? What kind of nerd stuff is that?? Let's put it all in one table.

How many columns are in that index? :-)

@spl0 literally the only that isn't used .. At all..

@spl0 its climate data per year per region... One region per row...

@azous wow.... good DB designer you have there!

@spl0 Was it just imported from excel or something? How many rows in there?

Look ma! Big data!

I can see someone doing that in excel. But taking the time to learn postgres to do that... It's crazy.

@spl0 387 rows 😂
I'm refactoring a lot of these tables, they let me rewrite the system from scratch.. Its much better now, this table is gonna die soon 😊

The guy has a serious relationship problem

@sam21s i was three posts down the feed when I got the pun.😂😂😂 Came back for the ++

I have a client who has something like this hundreds of columns in the same table. After some time the table didn't allow adding new columns any more. I had to split it to two tables but it broke some parts of their software (a proprietary one don't have code to change it only web interface to add columns or tables).

What would you do in this situation knowing that all columns define one row no duplicates or redundancy of data.

@hoody two words: run away

Create views on the table and make the proprietary software use these views or build an interface that converts the view format to the format the prop. software expects? @hoody

Why can't you split it into multiple tables, with the same key if necessary? What sort of data is it?

@spl0 this is what I did. But there's a lot of complicated things that doesn't work with this changes.
Some screens of the web interface needs some of the columns in one table to be populated of course. Other functionalities needs the same columns with others. I tried to separate the max of columns but there's still some functionalities that needs columns from both new tables.
Last thing I can do is to duplicate some columns to resolve all the problems.

The data is from a banking company, I don't know really what all columns mean to them.

@Lukas I can't build a new interface really. there's a lot of users and they don't expect to login or work on different platforms.
Part of the solution was to use views but I can't use them every where.

Maybe this tries to model the "entire world" in one table?