Trace: • Using Custom SQL Statements
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
jvx:server:storage:custom_sql [2020/06/15 11:56] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:server:storage:custom_sql [2020/07/22 13:19] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| </file> | </file> | ||
| - | If you want to add additional columns, it's better using a view. But if you use a view, the automatic link cell editor detection won't work because of missing metadata information. | + | If you want to add additional columns, it's better to use a view. But if you use a view, the automatic link cell editor detection won't work because of missing metadata information. |
| However, it's trivial to add missing metadata information: | However, it's trivial to add missing metadata information: | ||
| Line 38: | Line 38: | ||
| The statement will add a link cell editor for the columns EXT_PLAYER_ID and EXT_PLAYER_NAME (from the view). The link cell editor will read data from EXTINFO (table, view, etc.) and use ID and NAME column as display and selection values (JVx hides ID columns per default). | The statement will add a link cell editor for the columns EXT_PLAYER_ID and EXT_PLAYER_NAME (from the view). The link cell editor will read data from EXTINFO (table, view, etc.) and use ID and NAME column as display and selection values (JVx hides ID columns per default). | ||
| - | If you have a prepared storage for your link cell editor records, it's also possible to use following: | + | If you have a prepared storage for your link cell editor records, it's also possible to use the following: |
| <file java> | <file java> | ||