VistaDB 5
Properties  Methods 

VistaDB.DDA Namespace : IVistaDBDDA Interface
IVistaDBDDA Interface Members

The following tables list the members exposed by IVistaDBDDA.

Public Properties
 NameDescription
 PropertyUnique identifier assigned to this IVistaDBConnection. This ID should not be held across database connections or in multiple threads. (Inherited from VistaDB.DDA.IVistaDBConnection)
 PropertyDefault locale id to use by CreateDatabase (Inherited from VistaDB.DDA.IVistaDBConnection)
 PropertyGet or set timeout for lock operations in seconds. Default is 10 seconds, negative values reset to default. Max timeout is 1 hour. (Inherited from VistaDB.DDA.IVistaDBConnection)
 PropertyDefault page size in kilobytes to use by CreateDatabase (Inherited from VistaDB.DDA.IVistaDBConnection)
 PropertyGet or set policy for lock files. When it is true files, which correspond to specific table will not be deleted with its closing. It allows some performance increasing in multi-user environment. (Inherited from VistaDB.DDA.IVistaDBConnection)
Top
Public Methods
 NameDescription
 MethodInstantiates secure/unsecured DDA database object and creates it physically on hard drive  
 MethodOverloaded. Creates temporary memory backed database for use during a single session (exclusive mode only).  
 MethodInstantiates secure/unsecured DDA database object and creates it physically in isolated storage  
 Method (Inherited from System.IDisposable)
 MethodInstantiates secure/unsecured DDA database object and opens database file  
 MethodInstantiates secure/unsecured DDA database object and open database file in isolated storage  
 MethodOverloaded. Pack database to compress free space in the database (also used to upgrade to the current supported format). Packing requires a new exclusive connection, so all other connections to that database must be closed (including clearing all pools) from this and any other process.  
 MethodOverloaded. Pack a database in "Repair" mode: not aborting when errors are encountered but dropping data in order to move on. Should only attempt on a separate copy or with a separate backup of the database in case of excessive data loss from the Repair attempt. Repair is most useful for recovering from corrupted indexes with no other data corruption.  
Top
See Also