- Description
- How to use it
- Preconditions
- 1. Define the locale schema in your workspace in the corresponding DB folder
- 2. Add the parameter with the path in the
- 3. Add the parameter with the path in the in the environment section
Description
Storing schema definitions in a local file enhances accessibility and accelerates access speed, leading to improved performance for DataServer applications in networked environments when utilizing a local schema cache. The TailScale connection exists from the Gitpod environment to the local database on your own machine.
When OpenEdge starts a client application, it loads the schema for each database that the application requires into memory. Ordinarily, OpenEdge reads the schema from the database, which can be on a remote server. If the network is slow, or over the internet using a VPN such as Tailscale, this can increase startup time significantly.
You can shorten client startup time by building and saving a local schema cache file. A schema cache file is a machine-portable binary file containing a complete schema or subschema for an OpenEdge database. When you start a Build.One application with local schema cache files, the AVM reads the required schema for each database almost instantaneously from the local workspace rather than waiting for network or server traffic.
How to use it
Preconditions
- TailScale is installed and connected the locale server
- The local database server is connected in the workspace
- The locale server is known
1. Define the locale schema in your workspace in the corresponding DB folder
src/backend/DB/myDB/myDB.schema
2. Add the parameter with the path in the
- openedge-project.json
- pasoe.pf
-cache
eg.
-cache src/backend/DB/myDB/myDB.schema
3. Add the parameter with the path in the in the environment section
- base.docker-compose.yml
-schema
e.g.
-schema /workspace/config/myDB.schema
- Commit the changes and run a prebuild
Back to Documentation
Back to Home Page