Irreproachable argumentation, which in my humble opinion is little or nothing useful to those who want to enter in the diabolic world of SQL. Especially, if you have not yet managed to change the chip and find out that for example, you must carry out a program without using variables.
All the programming gurus I've read, agree that the best way to master a language (SQL is) is to read code from good programmers and I do not remember anyone who says that you ask in the forums when you have any questions, and the sad reality is that it is difficult to find examples of SQL, apart from being attentive to these pages where sometimes you learn a lot in the code of some answers. I understand and empathize absolutely with the O.P. and must add that in the documentation of SQLite, I have always missed examples and comments that, for example, can be found in the PHP doc. Just a thougth. -- A. J. Millan. > > ---- Mensaje original ---- > De: Stephen Chrzanowski <pontia...@gmail.com> > Para: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Fecha: Wed, 26 Jun 2019 10:18:29 -0400 > Asunto: Re: [sqlite] the sqlite3 documentation would be pretty good if > itwasn't tragic... > > I've always been perturbed by the term "Real World Examples". Because... well.. Everything is different from one building to the next. How I make my SQL calls is going to be different than the company across the street. Heck, even the guy sitting across from me will come up with a different way to get to the same answer. "Real world" examples are really hard to come by considering that there are soo so many "real world" types of information that needs to be asked for. There is no "standard" query to get the same answer. How I pull data out of SQLite (Or any SQL DBMS) is going to be different than how Dr Hipp, how Ryan, how Simon, or how any other regular user posts on here. There's thousands, if not MILLIONS types of queries to get the exact same answer for a very specific required answer. For instance, there's nearly an infinite number of ways to get the answer "42" out of a database, but a "real world" example doesn't exist because it can be done way too many ways. The best way to figure out SQL is to dive in, and ask lots of questions. If it breaks, find out another way. Post your query here, demonstrate what you've done to try and solve the answer to why you're getting the wrong answer, and explain what the answer should be. Learning anything is a process, and SQL is absolutely no exception to that rule. Or law for that matter. I've asked a few questions here that probably didn't make sense to anyone else in this forum, but were crystal clear in my head. Google, Ask, Metacrawler, Yahoo, and yes, even Bing, will get you a part of the way there, but none of those search engines will provide you a link to a single site that says "To get to that answer, you must go this route, there's no other alternative". (Ok, other than for syntax differences, you HAVE to go a route, but..) **Note: SQL has a "standard" but no one really follows it to the "T". You'll find different quirks between different engines and their languages. So a particular query may work on one engine or multiple engines, but, that same query may not work on one. Generally, though [ select 1+1; ] should return 2 on ALL SQL engines. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
