![]() ![]() But how often do you need to do that as anything other than an application developer?īut I still don't find any compelling reason for SSMS to interpret a LINQ-like syntax, or for some other type of tool to be created just so you can write ad hoc DML in LINQ instead of SQL. Aqua Data Studio provides comprehensive, scalable, cross-platform data management. I also agree that LINQ has significant advantages with respect to manipulating and serializing/deserializing objects within the context of a C# application. But is it actually worth it to redevelop the parser? I doubt it. It makes writing the query parser more complex for the RDBMS developer, but clauses are, by and large, wholly independent. Now, I agree that clause order for SQL is completely arbitrary, and that the restriction sometimes doesn't make queries the easiest things to write. ![]() However, since the topic was pure query syntax and you haven't actually given me any other reason that ad hoc queries would actually benefit from interpreting LINQ instead of SQL - within or beyond the scope of Intellisense - I don't really understand what point you're trying to make anymore. The real advantage of LINQ is that it's supported by C# and ASP.Net directly I don't disagree with anything else you're saying about C#, but that's why I said: ![]() The reason LINQ is structured the way it is, is for the very reasons I mentioned.Īnd I already said I don't find those reasons compelling. So you agree that the actual advantage of LINQ basically has zero to do with the syntax then? I mean, the only on-point thing you said was: The real advantage of LINQ is that it's supported by C# and ASP.Net directly, so you aren't tempted to write a program with string queries and concatenation like so many self-taught PHP/MySQL developers do. Than this: FROM tableName WHERE col1 = "abc" SELECT col2, col3, col4 Automate is the fifth menu (from left to right) in the Main Application Window. I might prefer to write this: FROM tableNameīut I'd rather look for this: SELECT col2, col3, col4 FROM tableName WHERE col1 = 'abc' Aqua Data Studios Query Window - SQL Automation menus rapidly increase the speed of writing a query. studio increase memory, aqua data studio export connections, aqua data studio sql, aqua data studio dark theme, aqua data studio cost, aqua data studio license, aqua data studio crack 18 Crack Full Serial Key is productivity software for database developers, DBAs, and analysts. Making SELECT suffer that fate seems like a poor idea. The start of a statement is visually pretty easy to find, but having to find where the WHERE or the ORDER BY clause starts isn't always easy with subqueries or functions. Putting the selected fields first is a lot easier to read going back later, IMO. You only write code once, but you have to maintain it forever. However, you're arguably sacrificing maintainability to make code writing a bit easier. I'm not arguing that LINQ isn't often a better syntax to write a query with, just that putting the field list last really isn't a large benefit. It also has the advantage of being executable in the middle of writing the query. honestly it's not that hard to write SELECT TOP 10 * and write your query from there and go back later. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |