Assumtion is the mother of all fuckups
-
More to the point, why do we insist on using f*** to represent what we all know it actually means? Same as c***; 99% of English speaking readers, I’d wager, know exactly what word this represents. What’s wrong with using cock up if we want to supposedly sanitise the written word? Asking for a friend! 😂
-
Damn! Even the shortened version of a male hen is obscured. I’m living in a world of censorship
How about the long version, cockerel?
Wrong is evil and must be defeated. - Jeff Ello
-
How about the long version, cockerel?
Wrong is evil and must be defeated. - Jeff Ello
-
More to the point, why do we insist on using f*** to represent what we all know it actually means? Same as c***; 99% of English speaking readers, I’d wager, know exactly what word this represents. What’s wrong with using cock up if we want to supposedly sanitise the written word? Asking for a friend! 😂
To answer your question, it's all about keeping the site white-listed in various filters employed by companies.
Wrong is evil and must be defeated. - Jeff Ello
-
I had a customer say to me once, "I won't know what I want until I see it." Yes, that is a direct quote. He was definitely the worst customer I have ever had but there are some serious contenders. The top two are both quite large companies and I do everything I possibly can to avoid buying their products.
...working with one of them right now...
-
...working with one of them right now...
-
Thank you!
-
Hmmm, never had that problem using identities. :laugh:
"Go forth into the source" - Neal Morse
But did you ever use an identity for a year table?
Wrong is evil and must be defeated. - Jeff Ello
-
But did you ever use an identity for a year table?
Wrong is evil and must be defeated. - Jeff Ello
Jörgen Andersson wrote:
But did you ever use an identity for a year table?
Yes, but only to define fiscal/business years. The situation described where the only other column is an int (assuming :laugh: ) containing the year is ridiculous. :)
"Go forth into the source" - Neal Morse
-
Jörgen Andersson wrote:
But did you ever use an identity for a year table?
Yes, but only to define fiscal/business years. The situation described where the only other column is an int (assuming :laugh: ) containing the year is ridiculous. :)
"Go forth into the source" - Neal Morse
You're gonna love this. It's a lookup table for fiscal years! :laugh:
Wrong is evil and must be defeated. - Jeff Ello
-
You're gonna love this. It's a lookup table for fiscal years! :laugh:
Wrong is evil and must be defeated. - Jeff Ello
Jörgen Andersson wrote:
It's a lookup table for fiscal years
In a previous response, you mentioned that the year table only has two columns. Am I to assume that a fiscal year is the same as a calendar year in your situation? Mine are not...customers either start their year June 1 or September 1.
"Go forth into the source" - Neal Morse
-
Jörgen Andersson wrote:
It's a lookup table for fiscal years
In a previous response, you mentioned that the year table only has two columns. Am I to assume that a fiscal year is the same as a calendar year in your situation? Mine are not...customers either start their year June 1 or September 1.
"Go forth into the source" - Neal Morse
No it isn't. It's from september to August. Mind, I never claimed the database is well designed. Everything, and I really mean everything except one table, is done using surrogate keys. Including many that doesn't need it. Just one table is done using a natural key, that isn't. Surrogate keys are a safe bet though. They're never plain wrong even if they're not necessarily the best choice. But it can get ridiculous.
Wrong is evil and must be defeated. - Jeff Ello