|
LOL Well, I graduated from ITT Tech in Seattle, WA in 1997. Hopefully, the code you're talking about above did not come from anyone tought by my professor. He was very strict on proper code practice, and placing things where they truly belong. However, I seemed to be the only guy there, besides my professor, who seemed to get it, so your post doesn't surprise me in the slightest.
Kyosa Jamie Nordmeyer - Taekwondo Yi (2nd) Dan
Portland, Oregon, USA
|
|
|
|
|
At my last job I had to work a such a mess except it was in VB6. The original programmer was clueless. It had Global variables all over the place. There were no arguments passed to any methods ever! Everything was a variable in a larger scope. And this was the core software for the entire business. 100 people used this every day.
I remember one section of code that had to import a bunch of records. It read a file line by line and inserted the records into the table with SQL (of course it didn't reference the columns so you can never add any columns to the table). On top of that it execute a select count(*) from tbl after each insert to display the count on the screen. It would take forever and the users would be complaining about the slow speed of the program.
I started looking for another job on my first day of work because I got 40 emails about problems with the program. Fortunately I was only there for about 6 weeks. What's funny is that I purposely did not put VB6 anywhere on my resume, not did I mention it in the interview because I HATE programming VB6. Yet they expected me to work on a VB6 application.
I didn't get any requirements for the signature
|
|
|
|
|
I used to work at a place where many of those things were done and no one saw anything wrong with it.
I switched to a better job.
Bill W
|
|
|
|
|
|
Any database table with a 1,000 columns should be flagged for restructuring. That is indeed a horror.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
Any database table with a 1,000 columns should be flagged for restructuring deletion.
Simon
|
|
|
|
|
Yes, and also terminate the database architect who came up with the idea.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
This is surely worse than the database of 991 tables that I am looking at....
|
|
|
|
|
darkelv wrote: the database of 991 tables that I am looking at....
Wow, there is also a summary table, I suppose.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
In my system, each participant is a row, and each response is a column.
I think he confuses relational databases with excel sheets
modified 12-Sep-18 21:01pm.
|
|
|
|
|
What's the difference?
|
|
|
|
|
Excel spreadsheets are prettier. Eventually, they'll upgrade their Oracle database to Excel.
|
|
|
|
|
hahaha !! Good 1 . My comment makes no sense but I just couldnt stop laughing lmao
|
|
|
|
|
was the title of this supposed to be a play on the old bgates joke of only ever needing 640k
|
|
|
|
|
neilmajithia wrote: was the title of this supposed to be a play on the old bgates joke of only ever needing 640
No, the title was a play on the Gates thing.
|
|
|
|
|
if i ever come across a table with sover 4000 columns id pack my desk, leave by the nearest fire exit and email in my resigation when i got home.
|
|
|
|
|
I felt dirty hitting Access's 255 column limit.
|
|
|
|
|
(again on the Gates thing...)
Well, 255 columns should be enough for anyone!
To hell with circumstances; I create opportunities.
|
|
|
|
|
TRCH (The Real Coding Horror) is in my opinion the database design.
As comparison... For performance reasons we have a separate database intended for read-access, to which we copy the data in a less relational manner. The result is a few flat tables with a horrible number of columns. Still the worst one only has 160 columns...
Despite everything, the person most likely to be fooling you next is yourself.
|
|
|
|
|
I am sorry to tell you that limitations like this exist in many places.
For example you can not display this data since DataGrids have a limitation of 65000 pixel width.
As you can see I marked this as news
Natza Mitzi
|
|
|
|
|
|
I am curious about what you will save in 1000 columns?
Greetings from Germany
|
|
|
|
|
Datamining apps require many precomputed columns one can easily reach more than 1000 columns
Natza Mitzi
|
|
|
|
|
I think the original poster was goofing.
What possible entity could have 4000 attributes?
I didn't get any requirements for the signature
|
|
|
|
|
For 1000 columns, all can be done is to emit a fatwa for the db "architect".
("Tell me, people, am I going insane?" - Black Sabbath - Sabotage, 1975, "Am I going insane (Radio)").
Nuclear launch detected
|
|
|
|