Not logged in : Login
(Sponging disallowed)

About: Step 8     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : schema:HowToStep, within Data Space : kingsley.idehen.net associated with source document(s)
QRcode icon
http://kingsley.idehen.net/describe/?url=http%3A%2F%2Fwww.openlinksw.com%2Foplweb%2F281e2bd5f79fdd250c1ec4a1f1074636%23step8

Click Continue to view additional preferences that can be set for the connection. Initialization SQL - Lets you specify a file containing SQL statements that will be run automatically against the database upon connection. Cursor Sensitivity - Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the 'High Cursor Sensitivity' checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. MaxRows Override - Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit. Disable AutoCommit - Changes the default commit behaviour of the OpenLink driver. The default mode is AutoCommit (box unchecked). Defer fetching of long data - Defers fetching of LONG (BINARY, BLOB etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in query do not include LONG data fields. Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema. Multiple Active Statements Emulation - Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver. Always include VIEWS in table list - This switch is needed for Microsoft Excel and Query, Stata, and some other tools which explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see VIEWs in the graphical query builder. This option is redundant when Always include alltypes is ticked. Always include alltypes in table list - This switch is needed for Microsoft Excel and Query, Stata, and some other tools which explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see SYSTEM TABLEs, VIEWs, SYSTEM VIEWs, SYNONYMs, GLOBAL TEMPORARYs, ALIASes, and/or LOCAL TEMPORARYs in the graphical query builder. Note: the TABLE list will be much longer than when this box is not ticked, and SYSTEM objects will be sorted to the top of the list, due to typical naming conventions. When finished, click the Finish button to save your new Data Source Name.

AttributesValues
type
Description
  • Click Continue to view additional preferences that can be set for the connection. Initialization SQL - Lets you specify a file containing SQL statements that will be run automatically against the database upon connection. Cursor Sensitivity - Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the 'High Cursor Sensitivity' checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. MaxRows Override - Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit. Disable AutoCommit - Changes the default commit behaviour of the OpenLink driver. The default mode is AutoCommit (box unchecked). Defer fetching of long data - Defers fetching of LONG (BINARY, BLOB etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in query do not include LONG data fields. Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema. Multiple Active Statements Emulation - Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver. Always include VIEWS in table list - This switch is needed for Microsoft Excel and Query, Stata, and some other tools which explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see VIEWs in the graphical query builder. This option is redundant when Always include alltypes is ticked. Always include alltypes in table list - This switch is needed for Microsoft Excel and Query, Stata, and some other tools which explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see SYSTEM TABLEs, VIEWs, SYSTEM VIEWs, SYNONYMs, GLOBAL TEMPORARYs, ALIASes, and/or LOCAL TEMPORARYs in the graphical query builder. Note: the TABLE list will be much longer than when this box is not ticked, and SYSTEM objects will be sorted to the top of the list, due to typical naming conventions. When finished, click the Finish button to save your new Data Source Name.
name
  • Step 8
position
is nextItem of
is schema:step of
Faceted Search & Find service v1.17_git139 as of Feb 29 2024


Alternative Linked Data Documents: PivotViewer | iSPARQL | ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3330 as of Mar 11 2024, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (7 GB total memory, 5 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software