You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following SQL statements are fed to the formatter:
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB 'Man*';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB '*Man';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB '?ere*';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB '*[1-9]*';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB '*[^1-9]*';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB '*[1-9]';
The dialect is SQLite.
The string literal that follows keyword GLOB should remain unchanged.
However, the output is as follows:
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB ' Man * ';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB ' * Man ';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB ' ? ere * ';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB ' * [1-9] * ';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB ' * [^1-9] * ';
SELECT
trackid,
name
FROM
tracks
WHERE
name GLOB ' * [1-9] ';
It would be nice to have a way to have the parser ignore certain SQL statements if there isn't a solution at the moment.
sleek version: 0.3.0
The text was updated successfully, but these errors were encountered:
The following SQL statements are fed to the formatter:
The dialect is SQLite.
The string literal that follows keyword GLOB should remain unchanged.
However, the output is as follows:
It would be nice to have a way to have the parser ignore certain SQL statements if there isn't a solution at the moment.
sleek version: 0.3.0
The text was updated successfully, but these errors were encountered: