Skip to main content

Timeline for Loading a Model from a Database

Current License: CC BY-SA 3.0

14 events
when toggle format what by license comment
Jun 6, 2015 at 11:42 vote accept JammoD
Jun 6, 2015 at 11:29 answer added RubberDuck timeline score: 2
Jun 6, 2015 at 10:41 comment added JammoD @RubberDuck I've asked that question many times and argued the point that it would be much better to separate it. Thanks for your assistance either way :)
Jun 6, 2015 at 10:30 history edited JammoD CC BY-SA 3.0
deleted 4 characters in body
Jun 6, 2015 at 10:18 comment added RubberDuck Data overload. They might think that's what they want, but has anybody asked if it would be better to show separate screens? In my experience, this is too much for a human brain to cope with (user or developer). If that's the requirement though, ok then. I get it. Business loves their spreadsheets.
Jun 6, 2015 at 10:11 comment added JammoD @RubberDuck Would that not be overkill if each CaseID can only have one set of information? As each case is a property and that property can only have one set of details. The business requirement for all the data is to be loaded into a screen to allow the staff to update and view the information for the property.
Jun 6, 2015 at 10:07 comment added RubberDuck Let me ask you something, what exactly do you plan on doing with all that data at once?
Jun 6, 2015 at 10:04 comment added RubberDuck Ahh. Well, I guess spreadsheet syndrome can manifest in different ways. I don't know how I would proceed because I have no idea what you're trying to do with the data. All I know is you're dealing with 13 distinct objects here and you've stuffed them into this one class. All I had to do was count the comments on the last snippet to tell that much.
Jun 6, 2015 at 9:56 comment added JammoD @RubberDuck I am intrigued how you can tell the database structure from that one model as I am not using Direct Table access with this method and have a stored procedure which is using many tables. I have then created a model based on that stored procedure. How would you proceed?
Jun 6, 2015 at 9:42 comment added RubberDuck It's not irrelevant at all. This looks horrible simply because your model is huge. I'm counting 13 distinct models shoved inside of that one you've got there.
Jun 6, 2015 at 7:32 comment added JammoD @RubberDuck I'm also the DBA, its a system that I have inherited and does requires some more normalisation but that's kind of irrelevant for this question as this is a Stored Procedure.
Jun 5, 2015 at 21:17 comment added RubberDuck Dude, you need to talk to your DBA about normalizing that table.
Jun 5, 2015 at 16:20 history edited Malachi CC BY-SA 3.0
fixed formatting and added a tag
Jun 5, 2015 at 16:15 history asked JammoD CC BY-SA 3.0