|
We have sufficient information to recreate the product, but neither the manpower nor the time to do so.
Software Zen: delete this;
|
|
|
|
|
..with all your due respect!!..
😇😇😇😇
|
|
|
|
|
Been there done this rewrite. Only in my case it was my boss's code that I rewrote. He had four entry points and I whittled them down to two - add() and delete(). Had to track down all the instances where he used the four entry points and rework those as well. Final code not only was about two thirds the size it executed about a third faster (very disk intensive).
|
|
|
|
|
Part 1
You probably know about jsfiddle and how you run and test your JavaScript in your browser.
But there is also a SQLFiddle which allows you to run and test your sql in your browser[^].
It's quite convenient.
Supports MySQl, Postgres, Sqlite, Oracle and Sql Server.
Also, if you work on a query, you can save the URL and get back to it.
Part 2
I recently discovered that you can do a select from two tables allowing you to select just the columns you want (versus a join). I don't know why that amazed me, but I'd never tried it before and it really helped in a current situation.
here's a very simplified sqlfiddle example:
SQL Fiddle[^]
edit
fixed initial link to sqlfiddle
modified 18-May-21 13:25pm.
|
|
|
|
|
Nice, but did you really intend to have a non-unique key in Address? 
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: but did you really intend to have a non-unique key in Address?
Oops! Updated the link (to the one where I fixed the key value in address).
Thanks
|
|
|
|
|
There are quite a few "fiddle" sites for different technologies: There's a fiddle for that![^]
However, steer clear of refiddle DOT com for the moment. The site seems to have been taken over by an Indonesian casino. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
If you didn't came across implicit join until now, then you better left it alone...
It will translate to a cross join but without the clear syntax of it...
It is not standard too (IIRC it started with MS Access)...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Quite standard Postgresql.
Which one of these you use is mainly a matter of style. The JOIN syntax in the FROM clause is probably not as portable to other SQL database management systems, even though it is in the SQL standard. For outer joins there is no choice: they must be done in the FROM clause. The ON or USING clause of an outer join is not equivalent to a WHERE condition, because it results in the addition of rows (for unmatched input rows) as well as the removal of rows in the final result.
|
|
|
|
|
MS SQL recognises that syntax as a JOIN and generates exactly the same execution plan.
|
|
|
|
|
Yeah, I think the main thing it helped me with was cleaning up my original Stored Proc query (which already had a bunch of joins). This helped me to easily add the one field I wanted without having to do all the join syntax and it ended up being a little cleaner.
|
|
|
|
|
There is also C# Online Compiler | .NET Fiddle[^]
raddevus wrote: do a select from two tables allowing you to select just the columns you want
Do not ever do this. It is a very, very old way of doing joins, before join syntax was a thing. It is an ancient form of writing sql. And it IS a join, just in the WHERE clause.
|
|
|
|
|
Good to know. Thanks. I've been reading about it and will do more research.
|
|
|
|
|
private string _CustomName = "Contact the developer";
public string CustomName
{
get
{
return _CustomName;
}
set
{
if (!_CustomName.IsNull())
{
if (!_CustomName.Equals(value))
{
_CustomName = value;
OnPropertyChanged("CustomName");
}
}
else
if (_CustomName != value)
{
_CustomName = value;
OnPropertyChanged("CustomName");
}
}
}
Not sure I want to contact the developer. 
|
|
|
|
|
It's custom-ary 
|
|
|
|
|
... and he forgot the StringEqualityComparison parameter in the Equals function...
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
Ridiculously long identifier of the day: Connect_catcher_line_to_PIC_ink_port__Connect_duct_line_to_PIC_storage_port__Then_Step_Up
All 90 characters of it. Yes, I created it deliberately and yes I know it includes two occurrences of two underscores in a row.
To make matters worse, it's an enum value, identifying a bit in a mask.
Thank [diety-of-choice] for IntelliSense.
Software Zen: delete this;
|
|
|
|
|
I would consider that a nominee as a potential candidate of the year. Nice effort. 
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Thanks. I have had longer ones (I remember a resource identifier that was close to 200), but this one set a recent record.
Software Zen: delete this;
|
|
|
|
|
Most excellent in every way! 
|
|
|
|
|
Thank you, thank you! I'm here all week. Try the veal, it's to die for!
Software Zen: delete this;
|
|
|
|
|
How about a GUID instead?! 
|
|
|
|
|
Looks like 3 bits in one.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
When I started Uni, we were told we had to have meaningful identifiers. This was back in the punched card days (80 cols per card). So, as a silent protest, I wrote my Assessed Practical Work with every identifier being exactly 80 chars long. This mean that each identifier took a whole punched card and made the program unintelligible as it was impossible to use indentation. (It had one good benefit - I could just duplicate the cards with identifiers and slot them into the source deck as required, so I only had to type them once). I passed the Assessed Practical Work as the program worked and it had meaningful identifiers, but they were not amused.
P.S. Language was Algol60 - one of the few languages that allowed spaces in identifiers - that helped make them meaningful but the code even less straight forward to read.
modified 6-May-21 4:34am.
|
|
|
|
|
At these days, we were working in PL1, which allowed free format, like C, with columns 9-72 of every card filled with a code. One programmer from our team liked to fill all this area with a code. Probably to save punched cards. To fix a bug, he needed to retype everything from the buggy card to the end. He didn't like a bugs in the beginning.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
