Difference between revisions of "Virtual Table Properties"
From Lianjapedia
Yvonne.milne (Talk | contribs) |
Yvonne.milne (Talk | contribs) |
||
Line 7: | Line 7: | ||
!width="30%"|Property||width="70%"|Notes | !width="30%"|Property||width="70%"|Notes | ||
|- | |- | ||
− | |valign=top|allowupdate|| | + | |valign=top|allowupdate||Allow updates: allowupdate=1 |
|- | |- | ||
|valign=top|autosync|| | |valign=top|autosync|| | ||
Line 44: | Line 44: | ||
|valign="top"|pagination||Enable pagination: pagination=1 | |valign="top"|pagination||Enable pagination: pagination=1 | ||
|- | |- | ||
− | |valign=top|password|| | + | |valign=top|password||Connection password |
|- | |- | ||
|valign=top|postfixwhere||Enable postfixwhere: postfixwhere=1. The WHERE clause will be applied to the resultset. | |valign=top|postfixwhere||Enable postfixwhere: postfixwhere=1. The WHERE clause will be applied to the resultset. | ||
Line 57: | Line 57: | ||
|valign="top"|rowid||Enable rowid: rowid=1 | |valign="top"|rowid||Enable rowid: rowid=1 | ||
|- | |- | ||
− | |valign=top|supportslimit|| | + | |valign=top|supportslimit||Specify that the backend database engine supports the LIMIT keyword: supportslimit=1 |
|- | |- | ||
− | |valign=top|supportsoffset|| | + | |valign=top|supportsoffset||Specify that the backend database engine supports the OFFSET keyword: supportsoffset=1 |
|- | |- | ||
|valign=top|table|| | |valign=top|table|| | ||
Line 71: | Line 71: | ||
|valign="top"|updatefieldlist||Comma-separated list of fields that can be updated. | |valign="top"|updatefieldlist||Comma-separated list of fields that can be updated. | ||
|- | |- | ||
− | |valign=top|username|| | + | |valign=top|username||Connection username |
|- | |- | ||
|valign=top|wheretype|| | |valign=top|wheretype|| |
Revision as of 11:28, 1 August 2016
Under Construction
See Also
ALTER VIRTUALTABLE, CREATE VIRTUALTABLE, CursorAdapter, Virtual Tables, Virtual Tables - Further Configuration and Troubleshooting, Virtual Tables - Local Development, Remote Deployment
Property | Notes |
---|---|
allowupdate | Allow updates: allowupdate=1 |
autosync | |
basetable | Name of the remote table. |
concatwhere | |
database | |
datasourcehost | |
datasourceoptions | |
datasourcehost | |
dbtype | The dbtype can be: lianja | mssql | mysql | oracle | postgres | vfp.
This makes connections faster as Lianja does not need to use heuristics to determine the remote database type. |
debug | Enable debugging: debug=1 |
fetchasneeded | Enable fetchasneeded: fetchasneeded=1 |
fetchsize | Specify fetchsize: fetchsize=N |
keepalive | Enable keepalive: keepalive=1 |
keyfieldlist | Synonym of primarykey. Used to uniquely identify the row for update and delete operations. |
maxrecords | |
nodata | Open without loading data: nodata=1 |
nosupportsoffset | Enable nosupportsoffset: nosupportsoffset=1 |
pagination | Enable pagination: pagination=1 |
password | Connection password |
postfixwhere | Enable postfixwhere: postfixwhere=1. The WHERE clause will be applied to the resultset. |
precision | Specify precision for float fields (default is 2): precision=N |
quotestring | The quotestring property is used to handle CRUD statements containing embedded ' characters. This should be set according to the requirements of the backend SQL engine. e.g. to replace single quotes by two single quotes for MSSQL: create virtualtable vtmssql_table properties "quotestring='';..." or to replace single quotes by \' for MSSQL: create virtual table vtmysql_table properties "quotestring=\';..." |
rowid | Enable rowid: rowid=1 |
supportslimit | Specify that the backend database engine supports the LIMIT keyword: supportslimit=1 |
supportsoffset | Specify that the backend database engine supports the OFFSET keyword: supportsoffset=1 |
table | |
translatename | Disable translation of remote table name (underscore to dot): translatename=false |
ttl | |
updatenamelist | |
updatefieldlist | Comma-separated list of fields that can be updated. |
username | Connection username |
wheretype |