|
It may cause NullPointException :
return Container.Find(instance => instance._id == _searchID)
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
Singleton!
- Compiler error at
=+ - Threading issues: susceptible to multiple instances being created
- Possibly a StackOverflowException while "get"ing the Query
- Possibly a NullReferenceException while "get"ing the Query
- Possibly a NullReferenceException while "set"ing the Query
- Should have a static constructor
Sascha Lefèvre wrote: Can you guess the intended purpose? Write a test-friendly class?
You have just been Sharapova'd.
|
|
|
|
|
Agent__007 wrote: Compiler error at =+
Really? That part of the code compiles for me.
It doesn't do what the author probably intended, but it compiles.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
Singleton is not thread-safe, Query property is potentially recursive, and can cause null exception. Also shouldn't query container contain list of Query instead of list of QueryContainer if QueryContainer is supposed to be a singleton (i.e. having only one). Also the whole class is crazy. Why have ID counter if you're using kinda "singleton"? Also no comments on what the class does or on public members. This IS Sparta!
|
|
|
|
|
Singleton is usually one of the first design patterns people learn. They immediately fall in love with it and are become blind for any other patterns out there.
I'd say the problem with this code would be that it causes brain damage.
|
|
|
|
|
I assume the intended purpose was to create a list of recently used queries. Even though the list was never actually filled (or allocated for that matter).
The good thing about pessimism is, that you are always either right or pleasently surprised.
|
|
|
|
|
Your warnings obviously weren't dire enough - he's back[^], with a modified version of the same class, which still doesn't fix his original problem.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Clue bat needed in Aisle 5! Clue bat needed in Aisle 5!
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Yes, I saw it.. sighed, and decided to let someone else answer since he apparently didn't believe me
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Among all the toe-curling flaws in there, these are my two favorites:
It's not even a singleton - it's a "noneton": Trying to access the Instance-property will cause a stack overflow due to recursion..
The List<QueryContainer> will be really, really short. Even when fixing the above flaw..
And the answer to the million dollar question:
It's supposed to somehow (don't ask me) help with fixing code that is vulnerable to SQL-injection.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
The new version[^] still doesn't fix the problem.
I'm running out of different ways to explain to him why his approach isn't going to work.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
He might be impervious to advice..
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I know one remarkably effective way to explain to him: use SQL Injection to delete his database. And every time he puts it back, it goes again.
It's cruel. It's nasty. It's probably illegal.
But it's what his best mate will do, just to see the look on his face...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Sascha Lefèvre wrote: It's supposed to somehow (don't ask me) help with fixing code that is vulnerable to SQL-injection.
After reading the actual questions, I don't think he is trying to fix the actual vulnerability with his code. Instead he may be trying to cheat the test system (by obfuscation) from detecting that there is an SQL injection vulnerability.
The good thing about pessimism is, that you are always either right or pleasently surprised.
|
|
|
|
|
"But please - no programming questions."
|
|
|
|
|
As you didn't mark your post as a joke or put a smiley into it I have to assume you're being serious: But my post isn't a programming question.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Here's your smiley:
Pick the one you like best. Only one per member.
|
|
|
|
|
|
I'll take the second one, please. Can you wrap it as a gift?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
******
* *
******
|
|
|
|
|
Very nice, will order again
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
With reference to this article[^], one of the young developer argued with me that the User object in asp.net application is singleton and Singleton class is used to store value in Session.
It might be looking funny, but its hard and time consuming to convince people if he has got partial/incorrect knowledge beforehand.
In my opinion, this kind of articles should be removed from codeproject as it misleads young developers.
Life is a computer program and everyone is the programmer of his own life.
|
|
|
|
|
I think it is called Singleton per session AFAIK.
|
|
|
|
|
Anurag Gandhi wrote: this kind of articles should be removed from codeproject as it misleads young developers I completely agree, and you will pleased to hear that it has now been deleted!
Don't forget that you can report articles as being "Inaccurate or Misleading"
|
|
|
|