Package generalDatabase.external
Class CopyTableSourceDefinition
java.lang.Object
generalDatabase.EmptyTableDefinition
generalDatabase.external.CopyTableDefinition
generalDatabase.external.CopyTableSourceDefinition
- All Implemented Interfaces:
 Cloneable
- 
Field Summary
Fields inherited from class generalDatabase.external.CopyTableDefinition
idMax, idMin, utcMax, utcMinFields inherited from class generalDatabase.EmptyTableDefinition
checkedConnection, indexColName, pamTableItems, tableName - 
Constructor Summary
Constructors - 
Method Summary
Modifier and TypeMethodDescriptionintaddTableItem(PamTableItem pamTableItem) Adds a new table itemvoidsetTableName(String tableName) Methods inherited from class generalDatabase.EmptyTableDefinition
clone, deblankString, findTableItem, findTableItem, getBasicSelectString, getCheckedConnection, getIndexItem, getSQLInsertString, getSQLInsertString, getSQLSelectString, getTableItem, getTableItemCount, getUpdatePolicy, isUseCheatIndexing, reblankString, removeTableItem, removeTableItem, setCheckedConnection, setIndexItem, setUpdatePolicy, setUseCheatIndexing, unpackResultSet 
- 
Constructor Details
- 
CopyTableSourceDefinition
 
 - 
 - 
Method Details
- 
getTableName
- Overrides:
 getTableNamein classEmptyTableDefinition- Returns:
 - Deblanked database table name
 
 - 
setTableName
- Overrides:
 setTableNamein classEmptyTableDefinition
 - 
addTableItem
Description copied from class:EmptyTableDefinitionAdds a new table item- Overrides:
 addTableItemin classEmptyTableDefinition- Parameters:
 pamTableItem- new table item object.- Returns:
 - The index of the new table item. Some columns are automatically
 added to every table, so the first column you create yourself may
 not be column 0. Since the number of columns added automatically may
 change in future versions of Pamguard, you should use this index when 
 adding data to the table using the SQLLogging.setColumnData function.
 
If an item already exists with the same name (after deblanking) the new table item will replace the old one. This is required for the annotation framework which is a bit fast and loose with recreating table items - without care, the item in the table definition will end up with a different reference to the item stored in the annotation code, so data will be written to the wrong tableitem when data are being prepared for storage.
 
 
 -