This was all .NET, but I remember using the latest DLL on my local box, and everything was okay for the 2 years I worked on it.
One of the leads before she left said that they might have used a script to generate all those variables, but that many parameters in a stored proc is crazy.
I remember them making a big deal about code quality, but their definition of quality was that it had to be OOP. I didn't bother asking, but I'd be curious to know why they harped on things that weren't a big deal while shrugging off stuff like this.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That is weird, maybe they were using an old version of the ODBC jar. This would drive me crazy seeing something like this.
This was all .NET, but I remember using the latest DLL on my local box, and everything was okay for the 2 years I worked on it.
One of the leads before she left said that they might have used a script to generate all those variables, but that many parameters in a stored proc is crazy.
I remember them making a big deal about code quality, but their definition of quality was that it had to be OOP. I didn't bother asking, but I'd be curious to know why they harped on things that weren't a big deal while shrugging off stuff like this.