SessionNoServer Constructor  | 
  
    Namespace: 
   VelocityDb.Session
    Assembly:
   VelocityDb (in VelocityDb.dll) Version: 11.1.0.0 (11.1)
Syntaxpublic SessionNoServer(
	string systemDir,
	int waitForLockMilliseconds = 5000,
	bool optimisticLocking = true,
	bool enablePageCache = true,
	CacheEnum objectCachingDefaultPolicy = CacheEnum.Yes,
	bool enableDatabaseCache = true
)
Public Sub New ( 
	systemDir As String,
	Optional waitForLockMilliseconds As Integer = 5000,
	Optional optimisticLocking As Boolean = true,
	Optional enablePageCache As Boolean = true,
	Optional objectCachingDefaultPolicy As CacheEnum = CacheEnum.Yes,
	Optional enableDatabaseCache As Boolean = true
)
public:
SessionNoServer(
	String^ systemDir, 
	int waitForLockMilliseconds = 5000, 
	bool optimisticLocking = true, 
	bool enablePageCache = true, 
	CacheEnum objectCachingDefaultPolicy = CacheEnum::Yes, 
	bool enableDatabaseCache = true
)
new : 
        systemDir : string * 
        ?waitForLockMilliseconds : int * 
        ?optimisticLocking : bool * 
        ?enablePageCache : bool * 
        ?objectCachingDefaultPolicy : CacheEnum * 
        ?enableDatabaseCache : bool 
(* Defaults:
        let _waitForLockMilliseconds = defaultArg waitForLockMilliseconds 5000
        let _optimisticLocking = defaultArg optimisticLocking true
        let _enablePageCache = defaultArg enablePageCache true
        let _objectCachingDefaultPolicy = defaultArg objectCachingDefaultPolicy CacheEnum.Yes
        let _enableDatabaseCache = defaultArg enableDatabaseCache true
*)
-> SessionNoServerParameters
- systemDir
 - Type: SystemString
The startup location directory path. Path can be an absolute (full) path or a path relative to s_baseDatabasePath - waitForLockMilliseconds (Optional)
 - Type: SystemInt32
The desired maximum lock wait time - optimisticLocking (Optional)
 - Type: SystemBoolean
Use optimistic locking. With optimistic locking, readers are always permitted and multiple updaters are permitted to update the same Databases/Pages but only the first transaction to commit or flush an updated Database/Page will be successful in making the commited chane. Other updaters will get an OptimisticLockingException if they try to commit/flush updates to the same Pages/Database.
            See http://en.wikipedia.org/wiki/Optimistic_concurrency_control for further explanation of optimistic locking. If optimistic locking is not enabled then pessimistic locking is used. See: http://en.wikipedia.org/wiki/Concurrency_control  - enablePageCache (Optional)
 - Type: SystemBoolean
If strong reference page caching isn't desired, turn it off by setting to false - objectCachingDefaultPolicy (Optional)
 - Type: VelocityDbCacheEnum
Determines default value of Cache - enableDatabaseCache (Optional)
 - Type: SystemBoolean
Is this session going to enable strong reference Database caching? 
See Also