ArbitraryQuery |
|
Car |
|
Car |
|
Car |
|
Car |
|
Car |
|
Car |
|
Car |
|
ClientServerExample |
|
CollectionsExample |
|
CollectionsExample.RetrieveCarPredicate |
|
CollectionsExample.RetrieveSensorReadoutPredicate |
|
ComplexQuery |
|
CultureInfoTranslator |
|
DeepExample |
|
EvaluationExample |
|
EvenHistoryEvaluation |
|
FirstStepsExample |
|
InheritanceExample |
|
LocalizedItemList |
A CultureInfo aware list of objects.
CultureInfo objects hold a native pointer to
a system structure.
|
NQExample |
|
NQExample |
|
OMEExample |
|
Pilot |
|
Pilot |
|
Pilot |
|
Pilot |
|
Pilot |
|
Pilot |
|
Pilot |
|
Pilot |
|
PressureSensorReadout |
|
PressureSensorReadout |
|
PressureSensorReadout |
|
QueryExample |
|
RetrieveAllSensorReadoutsPredicate |
|
SensorReadout |
|
SensorReadout |
|
SensorReadout |
|
SensorReadout |
|
SensorReadout |
|
ServerInfo |
Configuration used for StartServer and StopServer.
|
StartServer |
starts a db4o server with the settings from ServerInfo.
This is a typical setup for a long running server.
The Server may be stopped from a remote location by running
StopServer. The StartServer instance is used as a MessageRecipient
and reacts to receiving an instance of a StopServer object.
Note that all user classes need to be present on the server side
and that all possible Db4oFactory.Configure() calls to alter the db4o
configuration need to be executed on the client and on the server.
|
StopServer |
stops the db4o Server started with StartServer.
This is done by opening a client connection
to the server and by sending a StopServer object as
a message. StartServer will react in it's
processMessage method.
|
StructuredExample |
|
StructuredExample.RetrieveCarsByPilotNamePredicate |
|
TemperatureSensorReadout |
|
TemperatureSensorReadout |
|
TemperatureSensorReadout |
|
TemperatureSensorReadout |
|
TransactionExample |
|
TransparentActivationExample |
|
TransparentPersistenceExample |
|
Util |
|