etc statements) on the left and your query statments (the select, set. It is very easy to use: put your DDL and DML statements (the create, insert, update, alter. Here would be mine for the examples in this answer SQL fiddle and in DB Fiddle. Consider providing an SQL Fiddle or DB Fiddle This tells us not only what you want, but what you have tried, and you will get an answer a LOT faster. The issue I'm having is I need to filter not only by a status of 1 butĪlso by the phone number starting with 214 I have written the query up to this point, but am stuck on what to do next After showing what the data is like, you should also show what attempts you have made. Generally 5-15 rows is enough data for question readers to get a good feel for the data. This data should be minimized and just enough to show what you are working with. The first thing you should do is lay out some data for the community to visually see what you are working with. Give the Background - Relevant Data? Attempts? A. It's hard for us to look at a question that doesn't detail these things out, and understand what you want unless you provide some detail yourself! More specific problem statements will help attract better answers and even upvotes.Ģ. The GOOD examples are good ways to tell the community if you are running into an error or can't wrap your mind around the next step in your query. They give the community no help or guidance on what the error is. The BAD examples aren't problem statements. | "what happened" | "how do I do (whatever you need to do)" | | "it's not working" | "I'm stuck on the next part of this query" | | "it errors" | "It errors with the message (your error message)" | Problem Statement - What problem are you stuck with? +-+-+ There are key pieces of information that we need before we can help you and those would be the following points. When you write your question you are writing an essay. Writing a Good Question - Keep it Structured / Ordered If we need more information, we will let you know. Keep it brief, to the point, detailed, and include the specific snippet of code related. Please consider reading this about the basic technology, and this about indexing.Īsk yourself this question: If I have no idea about my system/setup/situation what is a simple way to describe it?ĭon't waste our time on loads of code or paragraphs of information when it is not directly related to the question at hand. (By contrast, most programming languages are procedural.) The various table servers contain elaborate query planners to work out the best way to get what you want. SQL describes what you want, not how to get it. If you're asking why something in SQL works the way it does, keep in mind that SQL is declarative, not procedural. Figure Out What is Essential For Us - Keep it Brief and Relevant
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |