Does everyone agree Stack Overflow is shit?
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
In these parts, it's known as SNARK Overflow.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
I have found a lot of inspiring tips and code pieces, but I agree that it is badly presented and sometimes a harsh tongue is there. But see the Q&A section of CP - there are also big differences. I got sometimes bad critics for working solutions. :~ And someone asked about his library but explicitly did accepted no redesign of his crap. :doh:
Press F1 for help or google it. Greetings from Germany
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
I feel SO has it's place in the interwebs. Both CP and SO have been useful to me on more than one occasion. I choose to ignore the rare snarky remark on account of all kinds of people free to use both platforms. I cases I can't ignore I report. That's about it.
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
I use it if results come up in Google searches. The couple of times I submitted questions were... unsuccessful :mad: X|.
Software Zen:
delete this; -
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
I’ve gotten more answers from SO Googling than any other website, bar none. Don’t see the reason for all the hate… which isn’t really helpful and compromises 90% of I see in the lounge.
Jeremy Falcon
-
I use it if results come up in Google searches. The couple of times I submitted questions were... unsuccessful :mad: X|.
Software Zen:
delete this;To be fair… the same can happen on CP. Reddit has been pretty good for me personally. Sometimes questions are a hit and miss there too. Some nerds love to pretend to know an answer they don’t. But that’s not site specific. Talent is hard to find in any field.
Jeremy Falcon
-
I feel SO has it's place in the interwebs. Both CP and SO have been useful to me on more than one occasion. I choose to ignore the rare snarky remark on account of all kinds of people free to use both platforms. I cases I can't ignore I report. That's about it.
Yup. SO is no more or less toxic than CP, Reddit, etc.
Jeremy Falcon
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
SO is not friendly for people asking questions, especially if one of their "elites" insist that you post code for a non-code question (as you found out). EF making assumptions is precisely why I hate and abhor ORMs of any description, and I rolled my own entity factory and DAL code (back in the day when I was still writing real code instead of this javascript crap I'm dealing with now). If you're interested and have the freedom to move away from EF, I've written some articles with regards to entity generation based on database contents, as well as a generic ADO assembly. It's all .net framework code, but you shouldn't have any probs moving it to .net core if that's a requirement. Entity Factory - Get Your ORM-less Freak On![^] Generic DAL for ADO.Net - A Revisit[^]
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
Yes, and no. It is a great repository of knowledge, and if you phrase your Google search correctly, it will often give you exactly what you want. OTOH, you must put on your asbestos underwear before asking a question there.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Yes, and no. It is a great repository of knowledge, and if you phrase your Google search correctly, it will often give you exactly what you want. OTOH, you must put on your asbestos underwear before asking a question there.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
Daniel Pfeffer wrote:
OTOH, you must put on your asbestos underwear before asking a question there.
It's the same thing with Reddit, CP, etc. too though. Nerds will be nerds. Which means most will pretend to know something they don't (and deflect with insults) and they love to be angry and argue. I mean, just look at the lounge... clearly they have unhappy people here too. Same goes for any tech site. Especially popular ones. We're supposed to be the mature, older group but I'd contest just older only. :laugh:
Jeremy Falcon
-
SO is not friendly for people asking questions, especially if one of their "elites" insist that you post code for a non-code question (as you found out). EF making assumptions is precisely why I hate and abhor ORMs of any description, and I rolled my own entity factory and DAL code (back in the day when I was still writing real code instead of this javascript crap I'm dealing with now). If you're interested and have the freedom to move away from EF, I've written some articles with regards to entity generation based on database contents, as well as a generic ADO assembly. It's all .net framework code, but you shouldn't have any probs moving it to .net core if that's a requirement. Entity Factory - Get Your ORM-less Freak On![^] Generic DAL for ADO.Net - A Revisit[^]
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013How is SO any different than the IRC days back in the 90s? Or the BBS days in the 80s? We're supposed to be mature, professional seniors here and yet we still think the problem is specific to one site? You ever ask a question on CP? You'll need to do the same exact thing with phrasing. Same thing goes with managing devs IRL, or anyone for that matter (including non-devs). And funny how people only come out of the wood works to complain. :suss: This is the part where you argue now...
Jeremy Falcon
-
I have found a lot of inspiring tips and code pieces, but I agree that it is badly presented and sometimes a harsh tongue is there. But see the Q&A section of CP - there are also big differences. I got sometimes bad critics for working solutions. :~ And someone asked about his library but explicitly did accepted no redesign of his crap. :doh:
Press F1 for help or google it. Greetings from Germany
KarstenK wrote:
I agree that it is badly presented and sometimes a harsh tongue is there.
As you mentioned (so I guess my post is pointless. :laugh:)... I've seen harsh tongue on CP too. The real problem is immature devs need to go outside more and interact with real humans. I bet you can guess which ones are prevalent on the maturity scale. :laugh:
Jeremy Falcon
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
BTW - the way to configure Postgres style naming is to use a snake name casing setting. Here's one I used earlier:
var connectionString = builder.Configuration.GetConnectionString("DefaultConnection") ??
throw new InvalidOperationException("Connection string 'DefaultConnection' not found.");
builder.Services.AddDbContext(options =>
{
options.UseNpgsql(connectionString, o => o.UseQuerySplittingBehavior(QuerySplittingBehavior.SplitQuery))
.UseSnakeCaseNamingConvention()
.ConfigureWarnings(warnings => warnings.Throw(RelationalEventId.QueryPossibleUnintendedUseOfEqualsWarning));
});You can also override the OnModelCreating to override the naming convention for your foreign keys:
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
// Apply the naming convention to all relationships
foreach (var relationship in modelBuilder.Model.GetEntityTypes().SelectMany(e => e.GetForeignKeys()))
{
relationship.SetConstraintName(relationship.GetConstraintName().Replace("_id", "_key"));
}
base.OnModelCreating(modelBuilder);
}But that's just CodeProject. Where people aren't always arsey and rep-hunting.
-
How is SO any different than the IRC days back in the 90s? Or the BBS days in the 80s? We're supposed to be mature, professional seniors here and yet we still think the problem is specific to one site? You ever ask a question on CP? You'll need to do the same exact thing with phrasing. Same thing goes with managing devs IRL, or anyone for that matter (including non-devs). And funny how people only come out of the wood works to complain. :suss: This is the part where you argue now...
Jeremy Falcon
I didn't say it was specific to SO. SO was merely the qualifying criteria for the discussion. Yeah, CP can be just as bad, but for different reasons. I don't see many/any homework questions (of the ilk, "I need you to do my homework for me) on SO, but that used to be a real problem here. Since I don't really haunt the Q/A section anymore, I don't know it it's still a problem. Besides that, we're talking about SO, not CP. Why are you so angry lately?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
StackOverflow is great for a certain class of questions. Anything more than simple things is hard to either ask a proper question or get a proper answer because there are too many variables.
CI/CD = Continuous Impediment/Continuous Despair
-
To be fair… the same can happen on CP. Reddit has been pretty good for me personally. Sometimes questions are a hit and miss there too. Some nerds love to pretend to know an answer they don’t. But that’s not site specific. Talent is hard to find in any field.
Jeremy Falcon
-
EF decides I have properties, for example a Widget class in an entry and if there's no FK it creates a WidgetId property. This despite were Posgress (all lower case) and we say Key instead of Id. I know of no way to modify or configure this feature and asked how to turn it off. I was asked for a code sample, I said no, this is a general EF feature and I want to turn it off. I got told they can't help without a specific code sample, and they turned my question off!!!! To be clear this happens even with auto generated code and is ALWAYS WRONG. I am happy to have an issue I need to sort out to access one property, based on auto generated nonsense, but I don't want NO ACCESS to a table because it will always invent columns in the SQL that I never claimed to exist.
Christian Graus wrote:
EF
"Well, there's your problem." -- Adam savage I've never used it, so I wouldn't know, but it seems like the kind of thing which is a reason not to use it. Some colleagues of mine also say that the tools they use require that everything have a primary key, even when it provides no benefit, and I tell them to get better tools.