Ok, this title may not make sense, but please bear with me :)
I recently found myself puzzled by something in FluentNHibernate: a weird mapping artifact was popping to say hello to classes it had no relatioship to. After scratching my head, banging it a bit against the desk, I proceeded to search for info.
After a while, I decided to ask the SO community:
I'm seeing seomthing really weird in a project using Asp.Net MVC on the NHibernate stack (that is FluentNhibernate, NHibernate, NHibernate.Search and Lucene.net)
I have two POCO classes (called here
AlsoReferencesThingie) that both reference a third object (called
Thingie, my naming convention is cold and efficient) and ...
And then the following happens, while I'm typing the question
- "Hey, I forgot to check the current versions, maybe that'll help..."
- "Mhhh, weird, i didn't notice that"
- "Wait a second, I have to add this info to the SO question"
- "Wow! I smell a rat!!!"
- "Victory! Problem solved!"
So here's where I'm at. I'm looking at a question I didn't ask, already formatted and mostly documented with solid facts. Seems like a waste to not ask it, but I already have the solution. What should I do with it?
- Ask it and answer it right away after?
- Keep it to myself; if I managed, others will?
What's the official take on these non-questions (let's call them facts)? Wouldn't that lead to people adding facts to the site, not coming back even in the case of a better answer, thinking that question and answer are a little capsule that shall not be broken? Because let's face it, even if somebody pointed out a better way, the way I've worked and sweated for may always seem sweeter...