/*No comment*/

I´m sorry to mess things up for you. But I have to recommend you have a look at Postgresql with Entity framework. It´s just awesome, very productive when writing code.

It´s easy to get that piece of information if you can reproduce or simulate the bug you are after. Which is the normal way to go, for me at least.

Interesting. I hate when it feels like its right in front of me but I fail to see it. I´m currently looking for that little piece of information.

Sounds abit like the one I´m wrestling with now. I´ve made a communications application which runs on 3 different computers where it mess up on only one computer every monday, sometimes every 2 mondays.(Bytes are being swapped and the numbers are wrong, tcp/ip). Cleaning buffers and restarting the socket solves it, until next monday or the monday after. I ran it on my own computer hooked to the system on the computer that mess up and it works. So its only on one PC that mess up, same config as the rest.

Not really, was just asking how it was in your case.

Sounds heavy. Was it your code to begin with?

True, I know there arent any unsolveable bugs. I want to know if you came across any unsolveable bugs to you. Ones that you were unable to fix or maybe someone didnt give you time for it.

Have you guys ever found a bug or misbehaviour that you were unable to correct? I´ve had a bug haunting me for weeks that makes me wonder if there are unsolveable bugs out there. I lack experience since ive only been coding proffessionally for 5 years. If you had one,what was it and what made you give up?

Ok, sorry.

Have you guys ever found a bug or misbehaviour that you were unable to correct? I´ve had a bug haunting me for weeks that makes me wonder if there are unsolveable bugs out there. I lack experience since ive only been coding proffessionally for 5 years. If you had one,what was it and what made you give up? (I´m coding in C#, thats why i posted it on this forum.)

Yeah i guess so. Thanks for your time and input.

I´m not gonna start a programming language war. My point was they shouldnt call it a web development course if they will spend 80% of the time making offline C# and java applications. It should be called "dip your toes into the programming water" course.

Jörgen Andersson wrote:

Whos guidelines are those?

That´s what a friend was fed from school (I´m not schooled). So I Assumed it was standard, mostly because it makes sense. Not that i trust the school since they had a web developer program with a C# winform ball game exam and didnt touch php at all.

Quote:

I would rather create a Sheet table with a status column, and let the production table and the control_measures table refer to it instead.

I wasnt clear in my explanation but that was what i meant on how to solve the normalization.

Quote:

Why do you move the "Sheets" to a new table, it's still the same entity, isn't it?

I will try to explain. The production table stores shifttime and orders. So a new record will be added on new shifts or new order. When they are producing the final product, they also measure,controls and package sheets in stacks. So instead of having sheets stored over order/shift I want to store it on each stack. (One record for each stack in control_measures which is related to their shifts production table). Storing sheets in control_measures gives higher "resolution" and better data to serve to our customers. But only possible when producing the final product.

Indeed, I can guess and i have. However, I could not foresee this change. I´m split because on one hand i have "normalization is the way to go" and on the other hand i have "code that works". At the moment i will keep a nullable column and when it works i will look at normalization and how that will affect current code. I also believe it will be easier for future coders if i follow the standard guidelines.

I´m kind of doing science here. No one has done this kind of system before and the company i´m working for have been turned down by programming firms doing production systems. To prepare database against future changes i would have to normalize every column since no one knows what or how things works until we have tested it. neither memory nor performance is an issue since we are talking about 6-10k records a year.

So you prefer to normalize even if it is just one column? Whats wrong with a nullable column? And yes, this is the current design, i´m expanding.

We have a production table with a column called sheets. When we are making the final product in our production, sheets will be stored in another table called control_measures. This means we will only store sheets in production when we are making the final product. I want to know what you guys think. Should I normalize and move sheets to a new table related to production or should i make it nullable as it is? I know the recommended way of doing it in relational databases is normalization. But still, I´m curious to know what you guys have to say about this.

I didnt know that. I´ve only tested it on W7.