Package generalDatabase
Class LogModules
java.lang.Object
generalDatabase.SQLLogging
generalDatabase.DbSpecial
generalDatabase.LogModules
Functions for writing a list of modules into any database as character data
 Runs at DAQ start, goes through the settings manager list and for each
 set of settings, it serialises the settings data into a binary array, this
 is then converted from binary data to 6 bit ascii data (using the character set
 from the AIS standard, which should be compatible with any DBMS). This character
 string is then broken up into parts invalid input: '<' 255 characters long and written to the 
 Pamguard_Settings table in the database. 
 
This will allow 1) an audit of exactly how Pamguard was configured at any particular time, 2) when looking at data offline, the database will contain all information required to reconstruct the Pamguard data model and displays, the database thereby becomes a self contained document of operations, there being no need to keep hold of psf settings files.
This will allow 1) an audit of exactly how Pamguard was configured at any particular time, 2) when looking at data offline, the database will contain all information required to reconstruct the Pamguard data model and displays, the database thereby becomes a self contained document of operations, there being no need to keep hold of psf settings files.
- Author:
 - Doug Gillespie
 - See Also:
 
- 
Field Summary
Fields inherited from class generalDatabase.SQLLogging
superDetLogging, UPDATE_POLICY_OVERWRITE, UPDATE_POLICY_WRITENEW - 
Constructor Summary
Constructors - 
Method Summary
Modifier and TypeMethodDescriptionvoidpamStart(PamConnection con) voidpamStop(PamConnection con) voidsetTableData(SQLTypes sqlTypes, PamDataUnit pamDataUnit) Callback function when new data are created that allows the user to set the data for each column.Methods inherited from class generalDatabase.DbSpecial
getDbControl, logDataMethods inherited from class generalDatabase.SQLLogging
addAddOn, clearAllAddOns, countTableItems, countTableItems, createDataUnit, createEarlyResultSet, createInClause, createViewResultSet, createViewResultSet, deleteData, deleteData, deleteData, deleteIndexedItems, deleteSubtableItem, deleteSubtableItems, doExtraChecks, double2Float, fillTableData, finalize, findClosestDataPoint, findLogger, getBaseTableDefinition, getEarlyLoadClause, getIdListUpdatClause, getLastLoadIndex, getLastLoadUID, getLastTime, getLoggingAddOns, getPamDataBlock, getTableDefinition, getTimesUpdateClause, getUIDMatchClause, getUpdatePolicy, getViewerCursorFinder, getViewerEverythingClause, getViewerLessThanClause, getViewerLoadClause, getViewerOverlapClause, getViewerUpdateClause, insertCursorRow, isCanView, isLoadViewData, loadDataFrom, loadEarlyData, loadEarlyData, loadLastDataUnit, loadSubtableData, loadSubtableData, loadViewData, loadViewData, loadViewerData, logData, logData, logSubtableData, prepareEmulation, prepareForMixedMode, readLastData, readMixedModeData, readNextEmulation, reCheckTable, reLogData, reLogData, removeAddOn, removeAddOn, reset, saveOfflineData, setCanView, setColumnData, setLoadViewData, setTableDefinition, setUpdatePolicy, transferDataFromResult, updateCursorRow, updateSubtable 
- 
Constructor Details
- 
LogModules
 
 - 
 - 
Method Details
- 
pamStart
 - 
pamStop
 - 
setTableData
Description copied from class:SQLLoggingCallback function when new data are created that allows the user to set the data for each column. Columns that have data which can be filled automatically (counters, primary keys and columns cross referenced to data in other tables) are filled automatically in fillTableData()- Specified by:
 setTableDatain classSQLLogging- Parameters:
 pamDataUnit-
 
 -