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
Copy file name to clipboardExpand all lines: docs/pages/general/rules.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ When using Source Orbit, you may find that you want to reference objects that do
75
75
76
76
> `no object found for reference 'COUNTRY'`
77
77
78
-
If you know those objects do exist but outside of this project, then you can use the `.objrefs` file in the project root to list those objects and if that object is a service program, you can also list the exports by indenting after the service program reference. Comments can start with `#`
78
+
If you know those objects do exist but outside of this project, then you can use the `.objrefs` file (references file) in the project root to list those objects and if that object is a service program, you can also list the exports by indenting after the service program reference. Comments can start with `#`
79
79
80
80
```
81
81
# Files that exist outside this project
@@ -89,6 +89,8 @@ UTILS.SRVPGM
89
89
toLower
90
90
```
91
91
92
+
If you use a references file, but you have source that defines the object, the source will take precedence over the reference and a log will be issued on the source.
93
+
92
94
## Service Programs and Binder Source
93
95
94
96
For service programs to be created, binder source must exist for it. Source Orbit will read the binder source, find all the referenced export functions/procedures and will find the correct module that exports them to create the service program.
@@ -110,6 +112,8 @@ CREATE OR REPLACE TABLE CUSORD (...)
110
112
111
113
## Embedded SQL in RPGLE C specs
112
114
115
+
**This section is not true as of Source Orbit CLI 1.1.0**
116
+
113
117
Source Orbit does not support embedded SQL (`exec sql`) used in a C spec. - no problem with mixed-format or free-format. We recommend:
114
118
115
119
1. converting the embedded SQL statements (`exec sql`) to not have C specs, or
0 commit comments