Why dialect awareness matters in SQL - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select all columns from the table named 'employees'.

SQL

SELECT [1] FROM employees;

Drag options to blanks, or click blank then click option'

A*

BALL

CCOLUMNS

DEVERY

Attempts:

3 left

💡 Hint

Common Mistakes

Using keywords like ALL or EVERY which are not valid for selecting all columns.

Writing the word COLUMNS which is not recognized in this context.

The asterisk (*) is used in SQL to select all columns from a table.

2fill in blank

medium

Complete the code to limit the number of rows returned to 5 in a MySQL query.

SQL

SELECT * FROM products [1] 5;

Drag options to blanks, or click blank then click option'

AROWNUM

BTOP

CFETCH

DLIMIT

Attempts:

3 left

💡 Hint

Common Mistakes

Using TOP which is used in SQL Server, not MySQL.

Using FETCH or ROWNUM which belong to other SQL dialects.

In MySQL, the LIMIT keyword is used to restrict the number of rows returned.

3fill in blank

hard

Fix the error in the SQL Server query to select the top 3 rows from the 'orders' table.

SQL

SELECT [1] 3 * FROM orders;

Drag options to blanks, or click blank then click option'

ALIMIT

BROWNUM

CTOP

DFETCH

Attempts:

3 left

💡 Hint

Common Mistakes

Using LIMIT which causes syntax error in SQL Server.

Using FETCH or ROWNUM which are not valid here.

SQL Server uses TOP before the number to limit rows, unlike LIMIT in MySQL.

4fill in blank

hard

Fill both blanks to write a PostgreSQL query that fetches 10 rows starting from the 5th row.

SQL

SELECT * FROM sales [1] 10 [2] 5;

Drag options to blanks, or click blank then click option'

ALIMIT

BOFFSET

CTOP

DFETCH

Attempts:

3 left

💡 Hint

Common Mistakes

Using TOP which is not supported in PostgreSQL.

Mixing FETCH with OFFSET incorrectly.

PostgreSQL uses LIMIT to specify how many rows to return and OFFSET to skip rows.

5fill in blank

hard

Fill all three blanks to write an Oracle SQL query that fetches 5 rows after skipping the first 10 rows.

SQL

SELECT * FROM employees [2] 10 ROWS [1] [3] 5 ROWS ONLY;

Drag options to blanks, or click blank then click option'

AFETCH

BOFFSET

CFIRST

DNEXT

Attempts:

3 left

💡 Hint

Common Mistakes

Using LIMIT which is not valid in Oracle.

Swapping FIRST and NEXT keywords.

Oracle uses OFFSET to skip rows and FETCH NEXT n ROWS to limit rows returned.

Practice

1. Why is it important to be aware of SQL dialect differences when writing queries?

easy

A. Because all SQL databases use exactly the same syntax

B. Because SQL dialects only affect database security

C. Because SQL syntax and functions can vary between database systems

D. Because dialects determine the color of the database interface

Solution

1. Step 1: Understand SQL dialects

   Different database systems like MySQL, PostgreSQL, and SQL Server have variations in SQL syntax and functions.

2. Step 2: Importance of dialect awareness

   Knowing these differences helps avoid syntax errors and ensures queries run correctly on the target database.

3. Final Answer:

   Because SQL syntax and functions can vary between database systems -> Option C

4. Quick Check:

   SQL dialect differences = syntax and function variations [OK]

Hint: Remember: SQL syntax varies by database system [OK]

Common Mistakes:

• Assuming all SQL databases use the same syntax
• Ignoring function differences between dialects
• Thinking dialects only affect security

2. Which of the following SQL statements is valid in SQL Server but invalid in MySQL due to dialect differences?

easy

A. SELECT CURRENT_TIMESTAMP;

B. SELECT GETDATE();

C. SELECT NOW();

D. SELECT SYSDATE();

Solution

1. Step 1: Identify function usage in SQL Server

   SQL Server uses GETDATE() to get the current timestamp.

2. Step 2: Check MySQL compatibility

   MySQL does not support GETDATE(); it uses NOW() or CURRENT_TIMESTAMP. NOW() works in PostgreSQL and MySQL, SYSDATE() is valid in MySQL but behaves differently.

3. Final Answer:

   SELECT GETDATE(); -> Option B

4. Quick Check:

   GETDATE() is SQL Server specific [OK]

Hint: Check function names carefully for each SQL dialect [OK]

Common Mistakes:

• Confusing SQL Server functions with MySQL/PostgreSQL
• Assuming all current timestamp functions are interchangeable
• Ignoring parentheses in function calls

3. Given the following SQL query run on MySQL, what will be the output?

SELECT LENGTH('Hello');

Note: LENGTH returns the number of bytes in MySQL.

medium

A. NULL

B. 6

C. Syntax error

D. 5

Solution

1. Step 1: Understand LENGTH function in MySQL

   In MySQL, LENGTH returns the number of bytes in the string. 'Hello' has 5 ASCII characters, each 1 byte.

2. Step 2: Calculate output

   Since 'Hello' is 5 bytes, LENGTH('Hello') returns 5.

3. Final Answer:

   5 -> Option D

4. Quick Check:

   LENGTH('Hello') = 5 bytes [OK]

Hint: Remember LENGTH counts bytes in MySQL, not characters [OK]

Common Mistakes:

• Confusing LENGTH with CHAR_LENGTH
• Expecting character count instead of byte count
• Assuming syntax error due to function name

4. You run this query on SQL Server and get an error:

SELECT * FROM users LIMIT 5;

What is the cause and how to fix it?

medium

A. LIMIT is not supported in SQL Server; use TOP instead

B. Syntax error due to missing WHERE clause

C. LIMIT requires parentheses in SQL Server

D. The table 'users' does not exist

Solution

1. Step 1: Identify SQL Server syntax for limiting rows

   SQL Server does not support the LIMIT clause; it uses TOP to limit rows.

2. Step 2: Fix the query

   Replace LIMIT 5 with TOP 5 in the SELECT clause: SELECT TOP 5 * FROM users;

3. Final Answer:

   LIMIT is not supported in SQL Server; use TOP instead -> Option A

4. Quick Check:

   SQL Server uses TOP, not LIMIT [OK]

Hint: Use TOP in SQL Server, LIMIT in MySQL/PostgreSQL [OK]

Common Mistakes:

• Trying to use LIMIT in SQL Server
• Adding WHERE clause unnecessarily
• Assuming LIMIT needs parentheses

5. You want to write a query that returns the first 3 characters of a string column named name. Which of the following SQL queries is ANSI SQL compliant and works correctly in both MySQL and PostgreSQL?

hard

A. SELECT SUBSTRING(name, 1, 3) FROM users;

B. SELECT LEFT(name, 3) FROM users;

C. SELECT SUBSTR(name, 1, 3) FROM users;

D. SELECT MID(name, 1, 3) FROM users;

Solution

1. Step 1: Check substring functions in MySQL and PostgreSQL

   Both MySQL and PostgreSQL support SUBSTRING(string, start, length) syntax.

2. Step 2: Evaluate other options

   LEFT() works in MySQL but not standard in PostgreSQL; SUBSTR() is supported in MySQL but less common in PostgreSQL; MID() is MySQL only.

3. Final Answer:

   SELECT SUBSTRING(name, 1, 3) FROM users; -> Option A

4. Quick Check:

   SUBSTRING() works in both MySQL and PostgreSQL [OK]

Hint: Use SUBSTRING() for cross-dialect string extraction [OK]

Common Mistakes:

• Using LEFT() which is not standard in PostgreSQL
• Using MID() which is MySQL-only
• Assuming SUBSTR() works identically everywhere