I write the SQL wrong every time.
-
I've found a very easy way to completely avoid making any mistakes in SQL: I don't use SQL.
What's SQL...? :-\
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
Pretend it is because you thought your were writing for the Jet Engine. (which uses this)
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
Always write the WHERE clause first, even if it doesn't need one. WHERE 1=2 is always a good choice until you've got the rest worked out. Me, what I usually screw up with is forgetting which database I'm on. Oh, you mean I just wiped the production database? Oops.
No dogs or cats are in the classroom. My Mu[sic] My Films My Windows Programs, etc.
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
I use Squirrel a redneck SQL; GIMME what I need FROM [table name] DELETE what I don't need FROM [table name]
VS2010/Atmel Studio 6.0 ToDo Manager Extension
Version 3.0 now available. There is no place like 127.0.0.1 -
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
-
Always write the WHERE clause first, even if it doesn't need one. WHERE 1=2 is always a good choice until you've got the rest worked out. Me, what I usually screw up with is forgetting which database I'm on. Oh, you mean I just wiped the production database? Oops.
No dogs or cats are in the classroom. My Mu[sic] My Films My Windows Programs, etc.
Solid advice but the ONLY time I ever use the delete command is to clear test database tables. I never use delete in production - everything is a log and if the user doesn't want to see it anymore a flag is set on the record. I was getting burned too often by people who would blame me for bad data. Every item and every change is logged and nothing is ever deleted. :^)
-
Solid advice but the ONLY time I ever use the delete command is to clear test database tables. I never use delete in production - everything is a log and if the user doesn't want to see it anymore a flag is set on the record. I was getting burned too often by people who would blame me for bad data. Every item and every change is logged and nothing is ever deleted. :^)
-
What's SQL...? :-\
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
Colin Mullikin wrote:
What's SQL...?
An advanced language for querying databases that doesn't involve tons of ridiculously intricate frameworks and mysterious black box middle-tier software. Preferred by people who break out in a rash anytime something becomes more about the architecture then getting stuff done. ;P
-
Colin Mullikin wrote:
What's SQL...?
An advanced language for querying databases that doesn't involve tons of ridiculously intricate frameworks and mysterious black box middle-tier software. Preferred by people who break out in a rash anytime something becomes more about the architecture then getting stuff done. ;P
MehGerbil wrote:
An advanced language for querying databases
Don't know if I would call it advanced.
-
Colin Mullikin wrote:
What's SQL...?
An advanced language for querying databases that doesn't involve tons of ridiculously intricate frameworks and mysterious black box middle-tier software. Preferred by people who break out in a rash anytime something becomes more about the architecture then getting stuff done. ;P
MehGerbil wrote:
Preferred by people who break out in a rash anytime something becomes more about the architecture then getting stuff done
Water, meet monitor. :laugh: :laugh:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
Personally I use extension methods when writing LINQ, not the SQL like syntax. Anytime I see the SQL syntax my mind goes blank.
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
But it's not really a 'bug thingy': You can select * (meaning all) or columns you name when selecting. When you Delete, it's the whole ROW, not columns, hence the */Column names aren't required. :-)
Think of how stupid the average person is, and realize half of them are stupider than that. - George Carlin
-
I use Squirrel a redneck SQL; GIMME what I need FROM [table name] DELETE what I don't need FROM [table name]
VS2010/Atmel Studio 6.0 ToDo Manager Extension
Version 3.0 now available. There is no place like 127.0.0.1They didn't teach us that variant in school... :laugh:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
Which is why I have replaced that with
SELECT COUNT(ROWID) FROM [table_name]
Sometimes that by itself will tell me all I need to know. :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
-
But it's not really a 'bug thingy': You can select * (meaning all) or columns you name when selecting. When you Delete, it's the whole ROW, not columns, hence the */Column names aren't required. :-)
Think of how stupid the average person is, and realize half of them are stupider than that. - George Carlin
-
I figured I was the only one so I was too embarrassed to ever post about it here. O.o
djj55: Nice but may have a permission problem Pete O'Hanlon: He has my permission to run it.
Yet you quote a DBA. :-D
-
Yet you quote a DBA. :-D
-
I got into the habit of making myself look at the thing I wanted to delete before deleting.
-
I'm so used to writing:
SELECT * FROM [table name]
That you can bet when it's time to delete I'll write:
DELETE * FROM [table name]
I no longer blame myself. I consider it a language design bug thingy.
If get in the habit of putting all your statements inside a transaction, then if you realize you made a mistake you can roll it back without affecting the table. Of course, you have to remember to commit the transaction in a timely manner, otherwise the table remains locked.
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
