Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Use a goto. It's one of the few cases where it's warranted.</p> <p>Here's an example. As you can see, it's a lot cleaner than a <code>while(0)</code>, and will make the compiler complain less with <code>-Wall</code>, too!</p> <pre><code>// Returns whether or not the condition failed, printing the // given error if it did. static bool verifyThat(bool condition, const char* error) { if(!condition) printf("%s", error); return !condition; } void validatePass() { FILE *fptr; char password[MAX+1]; int iChar,iUpper,iLower,iSymbol,iNumber,iTotal,iResult,iCount; //shows user password guidelines printf("\n\n\t\tPassword rules: "); printf("\n\n\t\t 1. Passwords must be at least 9 characters long and less than 15 characters. "); printf("\n\n\t\t 2. Passwords must have at least 2 numbers in them."); printf("\n\n\t\t 3. Passwords must have at least 2 uppercase letters and 2 lowercase letters in them."); printf("\n\n\t\t 4. Passwords must have at least 1 symbol in them (eg ?, $, £, %)."); printf("\n\n\t\t 5. Passwords may not have small, common words in them eg hat, pow or ate."); get_user_password: printf("\n\n\t\tEnter your password following password rules: "); scanf("%s", &amp;password); iChar = countLetters(password,&amp;iUpper,&amp;iLower,&amp;iSymbol,&amp;iNumber,&amp;iTotal); iUpper = ... iLower = ... iSymbol = ... iNumber = ... iTotal = ... if(verifyThat(iUpper &gt;= 2, "Not enough uppercase letters!!!\n") || verifyThat(iLower &gt;= 2, "Not enough lowercase letters!!!\n") || verifyThat(iSymbol &gt;= 1, "Not enough symbols!!!\n") || verifyThat(iNumber &gt;= 2, "Not enough numbers!!!\n") || verifyThat(iTotal &gt;= 9, "Not enough characters!!!\n") || verifyThat(iTotal &lt;= 15, "Too many characters!!!\n")) goto get_user_password; iResult = checkWordInFile("dictionary.txt", password); if(verifyThat(iResult != gC_FOUND, "Password used.")) goto get_user_password; printf("Your new password is verified."); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POLooping back to User Input Validation C
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USClark Gaebel
    1. USClark Gaebel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI never used a goto in this before,would this mean putting a goto after each validation error message.
      singulars
      1. PO
      1. USBrian J
    2. COUsing the && operator here is very good advice, but using `goto` is not. This is essentially a loop, so using a loop statement is the way to express this intention to a person reading your code. There are cases where a `goto` is required, but this is not one of them.
      singulars
      1. PO
      1. USMackie Messer
    3. COPlease, implement the code with a loop in your answer. Then let the OP decide which is clearer. I tried this type of validation with a loop many years ago, and it didn't look very clear at all - especially compared to the elegant goto solution. If you can figure it out, I'd love to see it!
      singulars
      1. PO
      1. USClark Gaebel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload