|
The guilty party said that he just copied/pasted the query from access. Trying to keep em away from things like the query designer though, I'm even getting em to make views with TSQL and not that bloody view designer...
|
|
|
|
|
I have been using MS SQL Server since it first came out (in the mid-nineties).
For the first few years we were using a set of Sybase manuals because we didn't have any SQL Server manuals (and Google was very unresponsive back then).
In those days, if you knew what the differences were between Sybase and SQL Server you were at Guru level.
But I have never used the "View Designer". The couple times I stumbled into it by accident, I got out of there ASAP.
To be honest, it's not that I disdain it's UI, SQL skills, or anything like that.
I just don't understand it. I have seen people who can go in there, make views, copy the SQL out to use elsewhere etc. I can't do that.
I have been coding SQL since the early 80's (DEC VAX RDB). I can code SQL queries faster than I can say what I am doing. But I don't get that View Designer.
|
|
|
|
|
LOL... feel that one, I started in Dataease and DB4...
|
|
|
|
|
I've seen the Access wizards generate SQL that looks like that.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
Gaaahhh!!!
I recently registered on a website that doesn't accept upper-case letters in a username/email-address.
So today I tried to log in -- all it does is tell me that the login failed. Over and over and over again.
Can't you at least do a freakin' ToLower on whatever the user entered?
|
|
|
|
|
|
den2k88 wrote: sent an e-mail with the registered password in clear-text (with all the implications on their storage method), Unicode-encrypted?
|
|
|
|
|
den2k88 wrote: * the "forgot passowrd" button sent an e-mail with the registered password in clear-text (with all the implications on their storage method),
So.. do they have fraud insurance to cover themselves when their system gets hacked?
|
|
|
|
|
I sincerely hope so. Better than that I hope someone hacks them and pays my insurance bill but that's not gonna happen.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
|
|
|
|
|
Name them and shame them.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Well, if Lloyd was a Genius he would have an insurance company with a misspelled Alliance.
Gosh this is almost CCC material.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
StringComparison.IgnoreOrdinalCase
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
digimanus wrote: StringComparison.OrdinalIgnoreCase
FTFY.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thank you
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
If they don't accept UpperCase in username/email, that's weird but still not too bad. Imagine they do accept it, AND insist on case-sensitivity when you log-in... "Bernie" != "bernie" - which one did I use?
E.g. with postgresql, string comparison is case-sensitive by default...
|
|
|
|
|
PIEBALDconsult wrote: upper-case letters in a username/email-address. There's your first problem.
But yes, a simple problem to fix.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
|
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???
|
|
|
|
|
|
null means it'll fall back to some default or setting, this is from the source:
modifiedOptions.RequireEncryption =
modifiedOptions.RequireEncryption
?? serviceClient.DefaultRequestOptions.RequireEncryption
?? BaseDefaultRequestOptions.RequireEncryption;
TableRequestOptions.cs:135[^]
Perhaps an enumeration would've made it clearer:
enum RequireEncryption
{
Default,
Yes,
No
}
|
|
|
|
|
But obviously the default for a bool (at the end of the day) will be false, if not stated otherwise...And if stated otherwise, than it should be part of the documentation...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
It's not a boolean, it's a Nullable<bool>. Assigning a value to the property basically says "ignore all settings and defaults and do whatever I tell you to do", whether that's true or false. So leave it to null to allow some configuration option to determine whether to require encryption, or assign a value to make sure it either requires encryption or not.
If it were a regular boolean, it would be impossible to determine whether the developer specified false or whether it's just the default value of a boolean. Nullable<bool> does allow for that.
Personally I would've chosen an enumeration, as it's much more verbose, but a Nullable<bool> does the trick as well.
|
|
|
|
|
+1 for the enumeration. It brings a lot more room for expansion and it isn't a PITA in serialization or marshalling.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
|
|
|
|
|
It could be good explanation if it wasn't around bool...and if wasn't around this specific code...
Did you see what the default value of the property (in BaseDefaultRequestOptions)? NULL...
But actually in the code (line 158) it turns to false...
Also the documentation states clearly that only true and false has meanings...
Such nullable bool has meaning in cases where you want to force the developer to make a choice, but in this code is a clear case of wasting CPU cycles...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
The method at line 158 is called ApplyDefaultsAndClearEncryption, which is internal as well. true and false do have meaning, as well as leaving it undefined a.k.a. leave it to some setting to determine whether the value will be true or false.
I agree the code is unclear (as well as the documentation), but it does serve its purpose. How would you otherwise suggest to fall back to a default (which may either be true or false)?
|
|
|
|