Skip to content

Commit 113ab75

Browse files
authored
Give clearer example of multiple query predicates in one ql file
The new names aren't great, so feel free to change them, but I think we do need an explicit example of updating two relations using one ql file.
1 parent 15989ce commit 113ab75

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/prepare-db-upgrade.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -59,14 +59,16 @@ extended.rel: reorder input.rel (int id, string name, int parent) id name parent
5959
// QLL library, and will run in the context of the *old* dbscheme.
6060
relationname.rel: run relationname.qlo
6161
62-
// Create relationname.rel by running the query predicate 'predicatename' in
63-
// relationname.qlo and writing the query results as a .rel file. This command
62+
// Create relation1.rel by running the query predicate 'predicate1' in upgrade.qlo
63+
// and writing the query results as a .rel file, and running 'predicate2' in
64+
// upgrade.qlo and writing the query results as a .rel file. This command
6465
// expects the upgrade relation to be a query predicate, which has the advantage
6566
// of allowing multiple upgrade relations to appear in the same .ql file as
66-
// multiple query predicates. The query file should be named relationname.ql and
67+
// multiple query predicates. The query file should be named upgrade.ql and
6768
// should be placed in the upgrade directory. It should avoid using the default
6869
// QLL library, and will run in the context of the *old* dbscheme.
69-
relationname.rel: run relationname.qlo predicatename
70+
relation1.rel: run upgrade.qlo predicate1
71+
relation2.rel: run upgrade.qlo predicate2
7072
```
7173

7274
### Testing your scripts

0 commit comments

Comments
 (0)