Timeline for What does Robert C. Martin mean by SQL being unnecessary?
Current License: CC BY-SA 3.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 28, 2018 at 14:40 | history | edited | Doc Brown | CC BY-SA 3.0 |
wording improved
|
| Feb 27, 2018 at 6:59 | comment | added | Doc Brown | @RBarryYoung: yes, I focussed on the core aspect of the question. The question in its current form is IMHO way-too-broad, especially after the OP tried to "improve" it by adding more and more additional question details about what Martin might have said and meant. | |
| S Feb 26, 2018 at 23:41 | history | suggested | Glorfindel | CC BY-SA 3.0 |
typo corrected
|
| Feb 26, 2018 at 21:47 | comment | added | RBarryYoung | This answer has little-to-nothing to do with the question about SSDs and SQL. | |
| Feb 26, 2018 at 21:35 | review | Suggested edits | |||
| S Feb 26, 2018 at 23:41 | |||||
| Feb 26, 2018 at 20:16 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 48 characters in body
|
| Feb 26, 2018 at 20:14 | comment | added | Doc Brown | @christo8989: I don't think it will make much sense trying to write one answer as a respond to all of what Martin has once written or said in his career. My answer was one to the question give in your title, explaining mostly how the blog post in the first link you gave should IMHO be interpreted. | |
| Feb 26, 2018 at 19:38 | comment | added | Barmar | @RobertHarvey Everything is relative. It's high-level compared to writing all the file accessing directly, but it's low-level compared to an ORM library (although some of these are just direct mappings of SQL clauses to function calls, so maybe they're about the same level). | |
| Feb 26, 2018 at 19:32 | comment | added | Robert Harvey | @Barmar: SQL is about as high-level as you can get, and Bob is asserting that it is patently unsafe. | |
| Feb 26, 2018 at 18:39 | comment | added | Barmar |
@Cubic Isn't this just a variant of the age-old debate between high-level and low-level languages? HLLs are safer and more productive, LLLs are more powerful. Hacks like asm in C let you have your cake and eat it. Some ORMs have similar escapes to raw SQL.
|
|
| Feb 26, 2018 at 18:23 | comment | added | christo8989 | @DocBrown One of Robert's thoughts is to stop using relational databases. I've heard him equate SQL to all relational databases. His suggestion is to use transactional databases (the first I've heard of this, kinda) instead of static data. So, I think he is also against relational databases in general and probably for multiple reasons. One other reason being the changing from HDs to SSDs. | |
| Feb 26, 2018 at 15:07 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 325 characters in body
|
| Feb 26, 2018 at 13:26 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 4 characters in body
|
| Feb 26, 2018 at 13:25 | comment | added | Doc Brown | @Cubic: any solution to the problems mentioned by Martin probably need to be less powerful or less easy to use than SQL - that's their blessing and their curse. | |
| Feb 26, 2018 at 13:21 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 16 characters in body
|
| Feb 26, 2018 at 13:05 | comment | added | Doc Brown | @Walfrat: yes, that is the typical kind of safer API I had in mind. However, using ORMs is always a tradeoff, they are definitely not a silver bullet. | |
| Feb 26, 2018 at 13:02 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 22 characters in body
|
| Feb 26, 2018 at 13:01 | comment | added | Cubic | Martin does specifically argue that the API to use should not be as powerful as SQL; His argument that the power of SQL is the problem, not a feature. The API he's arguing for should be application specific, and only be as flexible and powerful as the application absolutely needs, not more. He's specifically arguing against inventing another string based query language. | |
| Feb 26, 2018 at 13:00 | history | edited | Doc Brown | CC BY-SA 3.0 |
Grammar improved.
|
| Feb 26, 2018 at 12:32 | comment | added | Walfrat | At least we can avoid using it for any writing operation usually with what ORM-like stuff provide. As for querying the database, you can already do quite some stuff without writing your own SQL. Nowadays only "advanced" usage of the database capabitilies should require to write SQL or the use of complex datatype (graph, geographic datas, recursive). | |
| S Feb 26, 2018 at 11:03 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 273 characters in body
|
| Feb 26, 2018 at 11:00 | review | Suggested edits | |||
| S Feb 26, 2018 at 11:03 | |||||
| Feb 26, 2018 at 10:26 | history | answered | Doc Brown | CC BY-SA 3.0 |