Skip to content

Commit ad5bbc5

Browse files
committed
Bugs
1 parent 3a40d71 commit ad5bbc5

3 files changed

+4
-4
lines changed

Patterns Delimiter-Separated Values.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ parent: Design Patterns
66
permalink: /patterns/split-dsv
77
---
88

9-
Note that the scripts in this section rely on the SQLite JSON library. In the latest version of SQLite, the JSON library is part of the core and is included in the build by default. Until recently, however, JSON has been developed as a loadable extension, which was not part of the default builds. Verify that the JSON functionality is available before using/adapting code from this tutorial (for example, use these [queries](/meta/engine)).
9+
Note that the scripts in this section rely on the SQLite JSON library. In the latest version of SQLite, the JSON library is part of the core and is included in the build by default. Until recently, however, JSON has been developed as a loadable extension, which was not part of the default builds. Verify that the JSON functionality is available before using/adapting code from this tutorial (for example, use these [queries](../meta/engine)).
1010

1111
### Split delimiter-separated value strings via JSON
1212

Patterns JSON and DSV Output.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ permalink: /patterns/json-sql-output
88

99
Using JSON, rather than a record set, for encoding the returned data may also be more efficient due to the reduced number of required API calls. While SQLite API is usually fast, each returned value still costs several API calls. (Under certain circumstances, however, there might be a high SQLite-independent overhead for each API call.) Another important consideration is whether there are any potential side effects of data conversion between numeric and textual formats. Let us show a few examples.
1010

11-
Consider a modified query from the [Surrogate Variables](/patterns/variables#DSV-Query) section:
11+
Consider a modified query from the [Surrogate Variables](./variables#DSV-Query) section:
1212

1313
~~~sql
1414
WITH

Patterns Surrogate Variables.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ parent: Design Patterns
66
permalink: /patterns/variables
77
---
88

9-
Let us rewrite the previous [query](/patterns/split-dsv#DSV-Query) using common tables expressions (CTEs):
9+
Let us rewrite the previous [query](./split-dsv#DSV-Query) using common tables expressions (CTEs):
1010

1111
~~~sql
1212
WITH
@@ -17,7 +17,7 @@ WITH
1717
SELECT * FROM folders;
1818
~~~
1919

20-
Suppose we wish to turn it into a library query (as discussed [earlier]( /patterns/decoupling-sql)), which should split a generic string. For now, we ignore the potential presence of certain characters, such as backslashes and double quotes within the terms. Query interface:
20+
Suppose we wish to turn it into a library query (as discussed [earlier](./decoupling-sql)), which should split a generic string. For now, we ignore the potential presence of certain characters, such as backslashes and double quotes within the terms. Query interface:
2121

2222
- input - the string to be split and the delimiter;
2323
- output - a list of terms.

0 commit comments

Comments
 (0)