@@ -27,16 +27,16 @@ To use the Oracle JDBC Pkl Parser:
2727
28281 . Prepare a .pkl configuration file (see examples below).
29292 . Add this artifact to your application's classpath.
30- 3 . Reference the .pkl file in the JDBC URL.
30+ 3 . Reference the .pkl file and the parser type in the JDBC URL.
3131
32- The parser type is inferred from the file extension . In this case, it’s "pkl".
33- If the file name doesn’t include an extension, you can specify the parser explicitly using the parser option .
32+ The parser type can be specified using the ` parser ` option . In this case, it’s "parser= pkl".
33+ By default, the parser type is "json" .
3434All other options (like key, label, etc.) follow the same format as other providers.
3535
3636Example using the file configuration provider:
3737
3838``` java
39- jdbc: oracle: thin: @config - file: // {pkl-file-name}[ ?parser=pkl&key=prefix&label=value&option1=value1&option2=value2...]
39+ jdbc: oracle: thin: @config - file: // {pkl-file-name}?parser=pkl[ &key=prefix&label=value&option1=value1&option2=value2...]
4040```
4141
4242## Writing .pkl Configuration
7070#### URL (using file provider):
7171
7272``` java
73- jdbc: oracle: thin: @config - file: // myJdbcConfig.pkl
73+ jdbc: oracle: thin: @config - file: // myJdbcConfig.pkl?parser=pkl
7474```
7575
7676### 2. Using ` import `
@@ -103,5 +103,5 @@ config1 = (JdbcConfig) {
103103#### URL (using file provider):
104104
105105``` java
106- jdbc: oracle: thin: @config - file: // myJdbcConfig.pkl?key=config1
106+ jdbc: oracle: thin: @config - file: // myJdbcConfig.pkl?parser=pkl& key=config1
107107```
0 commit comments