|
NeverJustHere wrote: It's intellisense where it gets messed up. Select can't list relevant columns because the referenced tables haven't been entered yet. It's why LINQ is the other way around. FROM .... SELECT ...
That's not SSMS, it's the nature of the language. They can't do SQL radically different from the ANSI standard because nobody would use the product. Yeah, it's annoying, but you learn to deal with it, like with any other tool.
I personally think that SQL does stuff backwards from the way your typical developer thinks about coding. It's unfortunate that a lot of DBAs are not really qualified to write SQL code - and I've actually been told by a DBA (when asked about a SQL Server-specific technique) that he "wasn't a developer and couldn't help me". As a result, developers are forced into the SQL dev role as a result.
".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
|
|
|
|
|
honey the codewitch wrote: It's impossible to remember it without using it every day
I USE SQL every day a week (Ok 5 out of 7)... Still there are things I have to look-up...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
honey the codewitch wrote: The syntax is inexplicable
honey the codewitch wrote: It's impossible to remember it without using it every day,
As a long time web developer I feel that's true for most all languages. As a web developer I do html, css, javascript, jquery, xml, json, c#, and t-sql. I often have to google for syntax. But SQL is the one I probably look up least often.
|
|
|
|
|
The web is even worse.
And it's not true of most languages. Duck typing is for people that like spending all day debugging a typo. Hard types are for closers. Compilers keep people honest.
Real programmers use butterflies
|
|
|
|
|
I'm thinking that the people that designed COBOL had a hand in SQL?
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Asking SQL to be like C# ... One wonders why one doesn't simply do C# and LINQ to SQL.
I'm sure SQL was a lot purer 40 years ago; before the community got hold of it. The pureness is still there, if you choose to ignore the other stuff.
Quote: 1999 SQL:1999 SQL3 Added regular expression matching, recursive queries (e.g. transitive closure), triggers, support for procedural and control-of-flow statements, nonscalar types (arrays), and some object-oriented features (e.g. structured types), support for embedding SQL in Java (SQL/OLB) and vice versa (SQL/JRT)
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
modified 1-Nov-21 13:20pm.
|
|
|
|
|
The point of the exercise (in my case) was to get SQL to do non-trivial field validation on strings - to verify at the final tier as well as the middleware.
Real programmers use butterflies
|
|
|
|
|
IMHO...
SQL is for optimized for data storage and retrieval, not field validation (beyond making sure a string isn't too long for the column you're storing it in). The middleware is always going to be better at transforming/validating the data. By the time you get to saving the data, it should already be valid because at some point,you have to just "go with it" and assume the data you're working with is okay.
".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
|
|
|
|
|
Which is fine until your middleware is compromised or buggy.
Plus I like wherever possible to keep the rules enforcing the integrity of the data in the database itself, that way the database is a complete standalone unit in terms of operating to a spec.
I know what you're saying. I hear you. I just also think that when you can get away with it, you *should* be validating in the DB tier as well.
Real programmers use butterflies
|
|
|
|
|
VS2022 has preview version. I have the latest preview.
It also has RC which, it turns out, are different product to preview. Now I have preview 7. And RC3 was just released at the same time. And what is the difference between both I wonder?
It feels like it was just meant to confused me... :/
|
|
|
|
|
Now you know why I wait. 
Real programmers use butterflies
|
|
|
|
|
Such wisdom and patience! 
|
|
|
|
|
First service pack or second?
I used to enjoy riding the bleeding edge, but it's been decades since I enjoyed being a beta (or alpha) tester!
|
|
|
|
|
Usually the 1st. I'm not ultra paranoid. I used to avoid anything with version "4" in it coming from microsoft as to this day .NET 4.x is maybe the only version 4 of anything they've produced that was solid, but medication helps.
Real programmers use butterflies
|
|
|
|
|
"Preview" means "Riddled with bugs we're working on"
"RCx" means "Riddled with bugs we're not going to fix."
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
The RC version is meant for production use and will continue to get the production releases going forward. These are fully supported by Microsoft.
The Preview version is not for production use and will get continue to get future preview releases of the product going forward. Preview releases may have experimental features that may not make it to the release version.
|
|
|
|
|
I've personally never bothered with VS betas.
The release versions are already buggy enough, why compound the problem? What feature is so compelling that you have to have it now?
|
|
|
|
|
RC will be the final thing, the first public release supported version.
Preview will be always preview of what (maybe) will be in the next released version. For those whose code requires the bleeding edge features (remember the span datatype). So after the first release it will immediately include the next steps.
A glimpse of the future: The released versions of VS 2019[^]
|
|
|
|
|
I cannot use this version (yet) because there is no Prism template pack for it yet. When I raised the issue on their blog site, Brian Lagunas himself responded that they will not create a Prism version for VS2022 while it is still a preview version - too many pitfalls. Lagunas is a wise man! 
Get me coffee and no one gets hurt!
|
|
|
|
|
RC=release candiate
Releasing an RC, a software developer says "please take a loot at this. I'm fairly confident for this to be a good rendition of the final product"
Releasing a preview, a developer says "this is not done. THIS IS NOT DONE! I promise you for this thing NOT to be production-ready by any stretch".
|
|
|
|
|
Use RC unless you want to code MAUI (or some other non-release tech) - MAUI is still in preview and is only available with the preview VS2022.
|
|
|
|
|
I had one day off.
Logging on Monday (BTW, just became an employee instead of contractor, with same pay, yeah me!), I synced the code and.....
Downloading 57,870 new files... 
Just a Monday here 
|
|
|
|
|
Someone probably checked in the downloaded files from a "hello world" web project.
|
|
|
|
|
And you need all those files, or could you not work off of a (still buildable) subset of that?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
