|
Name |
abahistsysobjects |
|
Code |
ap_hso |
|
Creation Date |
13 december 2000 13:53:05 |
|
Modification Date |
23 november 2011 14:24:41 |
|
Comment |
History of all objects ever loaded to the database. |
|
This table holds the history of abasysobjects. All objects that appear, or have appeared, in abasysojects will have one or more entries here, so you can retrieve the entire history of an object. |
|
|
|
Data |
NOT |
F |
|
|
objname |
|
sysname |
X |
|
Name of the object. |
|
|
datetime |
X |
|
When object was loaded. |
|
|
char(3) |
X |
X |
Object type. |
||
|
|
bit |
X |
|
The load was a DROP only. |
|
|
varchar(30) |
|
X |
Subsystem the object belongs to. |
||
|
|
int |
|
|
Version number in source control. |
|
|
varchar(15) |
|
|
Version-control label. |
||
|
nvarchar(250) |
|
X |
Path for VC-repository |
||
|
nvarchar(250) |
X |
|
Path in VC or on disk. |
||
|
varchar(64) |
X |
|
Script or tool that loaded the object. |
||
|
username |
nvarchar(40) |
X |
|
Name of NT user that loaded the object. |
|
|
hostname |
nvarchar(40) |
X |
|
Name of host from which the object was loaded. |
|
|
domain |
nvarchar(40) |
X |
|
On which domain the user was logged into. |
|
|
nvarchar(180) |
X |
|
Filename in AbaPerls directory structure. |
||
|
varchar(10) |
X |
|
File extension. |
|
Name |
Columns |
Options |
PK |
|
pk_ap_hso |
objname, loadtime | clustered |
X |
|
Name |
Columns |
Unique |
Clu |
PK |
FK |
AK |
|
aba_hso_loadtime_ix |
loadtime, objname |
X |
|
|
|
|
|
aba_hso_label_ix |
ss_label |
|
|
|
|
|
|
aba_hso_path_ix |
path |
|
|
|
|
|
|
Date and time when the object last was created or altered in the database. |
|
What kind of object. See abaobjecttypes for a list of the object types that AbaPerls handles. |
|
Whether this entry in abahistsysobjects corresponds to a deletion of the object. That is, the object was dropped, but not recreated, and thus the row for the object was deleted from abasysobjects. |
|
Which subsystem the object belongs to. NULL if the object was loaded with ABASQL without the -subsystem switch, or beause the object was loaded into abasysobjects with ap_zz_sob_load_sp. |
|
The version number in the version-control system of the file from which the object was loaded. NULL if the object was loaded from disk, typically by ABASQL. If the colunm is NULL, but ss_label has a value, this indicates that someone forcefully set ss_version to NULL, probably to be able to circumvent the checks for production or test databases. |
|
The argument specifed with the -label switch with the load tool (ABASQL, DBBUILD or an update script generated by DBUPDGEN). Most of the time it will be an AbaPerls labels on the form LetterMajor.Middle.Minor, but it does have to be. |
|
Path to the VC repository (e.g. SourceSafe or TFS database) the object was loaded from. NULL if object was loaded from disk. The path normally starts with a designator for the version-control system, but this may be missing for legacy data from the days when AbaPerls supported SourceSafe and nothing else. |
|
The path to the directory in which the file from which the object was loaded resided. This can either be a path in the VC repository or a the path on disk. |
|
Name of the update/patch script or the build tool that performed this load of the SQL object. |
|
Name of the file from which the the object was loaded. This is a name within the AbaPerls directory structure, for instance SUB/SOME_SP.SP. |
|
The file-extension part of filename, extracted to a column of its own to permit filtering, sorting etc. Is XXX for entries loaded by ap_zz_sob_load_sp. |
|
Parent Table |
Foreign Key Columns |
|
objtype |
|
|
vc_repository |
|
|
subsystem |
|
|
|