Domain: sql-info.de
Stories and comments across the archive that link to sql-info.de.
Comments · 200
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
Discussion of MySQL should include MySQL gotchas:
Any discussion of MySQL should include MySQL gotchas:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjust - 1.
General SQL
-
MySQL Gotchas
Did it fix any of the MySQL Gotchas?
-
Re:If you would RTFA...
If only it were MySQL just lacking features that would, after much mudslinging at the ideas themselves, be grudgingly retrofitted into a new table type. MySQL's brokenness goes deeper than that.
MySQL's attitude toward data integrity can be summed up as "if the constraint can't be satisfied, do it half-assed anyway". I find myself having to write application code to manage data integrity with MySQL, something I can take for granted with a real database. -
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
MySQL quirks
I find the MySQL gotchas frightening:- 1.
General SQL
- 1.1 NULL, or when NULL IS NOT NULL
- 1.2 AUTO_INCREMENT
- 1.3 ENUM
- 1.4 Case sensitivity in CHAR / VARCHAR fields
- 1.5 Variable length CHAR fields
- 1.6 VARCHAR's trailing blank allergy
- 1.7 DEFAULT NOW()
- 1.8 INSERT INTO
... SELECT ... - 1.9 Comments beginning with --
- 1.10 UNION and literal values
- 1.11 Division by zero
- 1.12 'concatenation' || 'or'
- 1.13 What goes in - isn't (always) what comes out
- 1.14 February 31st
- 2. Database Definition
- 3. Foreign Keys and Referential Integrity
- 4. Transactions and InnoDB tables
Don't read this: Slashdot lameness messages are very annoying when you have posted a legitimate comment: Your comment has too few characters per line (currently 18.5). Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "poster-comment" compre55ion filter. Try less whi7espace and/or less repetition. Comment aborted. Your commen7 has too few characters per 1ine. Your comment has too few characters per line (currently 18.5). Your comment violated the "poster-comment" compre66ion filter. Try less whitespace and/or less repetition. Comment aborted. Your comment has too few characters per line (currently 18.5). Your comment has too few characters per line.
Now it says: Your commen7 has too few characters per line (currently 33.7). However, I didn't change the number of lines.
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your - 1.
General SQL
-
Re:Duh!
Need a particular reason? Take your pick. http://sql-info.de/mysql/gotchas.html
-
Re:forcing MS branded everything is just bad buisn
Without getting into a db religion war, I fail to see how comparing mysql to sql server is "ludicrous." Both are enterprise level databases that have been used to some degree of success for large projects.
It's ludicrous because you're mistaking MySQL for an enterprise-level database system. It's not. It's a great, fast indexing and storage system for simple data sets, and it's been shoehorned into other roles where a better database would be more appropriate simply through propaganda (if I say "open source database", you immediately say "MySQL", and not the more featureful and robust "PostgreSQL") and ignorance. How many times have you seen the infamous MySQL errors from Slashdotted web pages? The bandwidth is obviously still there, else the pages would be giving errors about having exceeded their maximum limit or some such, but MySQL has taken a crap because it couldn't handle the load. Now, how many times have you seen a similar problem with Postgres-, Oracle-, SQL Server-backed sites? Why do you think Slashdot has had so many problems? Most of Slashdot's technical problems stem from their MySQL backend, and its inability to scale to a complex data set or large number of concurrent users (it's also the reason why most of Slashdot's pages are static pages, rather than rendered on the fly, because MySQL can't keep up with the load).
Would you trust your money to a financial institution that uses MySQL? I wouldn't, and not for any silly reason like because MySQL is open source. MySQL has problems, and the MySQL developers are arrogant enough to say that a lot of MySQL problems and deficiencies are "by design" and would slow down the system if they were implemented properly (maybe true, but if that's the case then MySQL is poorly written to begin with). MySQL is great for a hobbiest database, or for getting your feet wet with SQL (though you'd want to move to a more standards-compliant RDBMS before you get too deep, else you'll be learning MySQL-specific tricks and hacks that you'll then try to apply to other RDBMSs that don't need them), but it is not enterprise-level, regardless of what the open source zealots will tell you.
It supports the same language with minor syntax differences.
That's not exactly true, as Visual Studio
.NET still obviously supports C++ (Managed and standard). However, you're confusing VS.NET the development environment with .NET the platform. VS has had hooks for a long time to be able to add support for new languages. As well, you're confusing the MS Development Environment program (the IDE you're calling "Visual Studio .NET") with Visual Studio .NET the suite of tools. As I mentioned, VS.NET Architect has a lot of other tools and capabilities than VS.NET Professional (the de-facto "just the IDE, maybe a few extra things like Crystal Reports" suite, if you can't get the more barebones Academic version). Read through those pages. Architect does everything Professional does and more (yes, they're full of marketing speak, but read between the lines). Professional may be a more accurate comparison with BOA, but not Architect. -
Re:Technology in infancy...
OpenSource? I'm building my applications using Linux (standard POSIX), using MySQL (very standard SQL)
MySQL may be a useful program for many applications, but it certainly isn't 'very standard SQL'. -
Re:Access versus SQL
Not to mention these wonderful bits.
-
Re:A TOOL IS YOU
Please explain any of these.
-
Re:Never used PostgreSQLSubqueries are being added in MySQL 4.1, which is in alpha. I use MySQL every day, so can't wait for 4.1 to hit production.
Don't get your hopes up too much. I'd imagine their first implementation will suck. That's partially based on my distrust of the MySQL developers' abilities and partially based on a few comments I saw in the documentation you linked to:
Starting with version 4.1, MySQL supports all subquery forms and operations which the SQL standard requires, as well as a few features which are MySQL-specific (from here)
I'm suspicious of their MySQL-specific features. In the past, many MySQL-specific features have been dumb. I couldn't find specific mention of these ones, but I bet they're more of the same.
MySQL's unofficial recommendation is: avoid correlation because it makes your queries look more complex, and run more slowly. ( from this page)
Ugh! I use correlated subqueries all the time on Oracle and PostgreSQL with no performance problems. I'd guess from their comment that they're firing the subquery on every row of the outer query (which would run very slowly indeed). I think real databases replace these with equivalent but dramatically more efficient forms. (Like an "exists" subquery becoming another join condition and a distinct. Or a "not exists" subquery becoming a left join checking for nulls. Or however they implement it - it doesn't really matter; I type in something that is easy for me to understand/verify is correct, and they worry about making it perform well.
The PostgreSQL people were thinking about this sort of thing in 1997. And hell, they just now got IN/NOT IN to have good performance.[*] And they're good at this sort of thing. I don't have a lot of faith in the MySQL people.
ERROR 1235 (ER_NOT_SUPPORTED_YET)
SQLSTATE = 42000
Message = "This version of MySQL doesn't yet support 'LIMIT & IN/ALL/ANY/SOME subquery'"
(from here)So it's obviously not a complete implementation.
[*] - They probably could have gotten it to work a while ago but didn't because there was a workaround. (IN/NOT IN doesn't do anything EXISTS/NOT EXISTS can't, although IN/NOT IN is more terse.) Still, it shows you that there are likely to be a lot of gotchas in a new implementation.
-
Re:Rock on!
Show them this:
MySQL Gotcha's
If they still don't seriously consider at least switching away from MySQL, I would be very scared.
-
Why use PostgreSQL over MySQL?
Because they care about your data, among other things! You could have the fastest database server in the world, but if you find your data is corrupt, or truncated without warning, it doesn't do you much good.
Here is huge list of MySQL Gotcha's that absolutely floored me when I first read it. In my opinion, a "gotcha" in regards to a database is a "Bad Thing(tm)"
MySQL Gotchas"