Highlighted
Absent Member.
Absent Member.
368 views

SCHEMA: Attribute vs. data object


All,

In our current event design, the terminal name of any data container is
set to TargetDataName, and then all "parent" containers are listed,
slash-separated, in TargetDataContainer. This is true for tables in
databases, files in directories, attributes inside of directory objects
or classes, anything.

Others have suggested, however, that "attributes" or "properties" might
be a fundamentally different kind of data container, and should be
treated as such. So this would be things like attributes on a directory
object, file streams on an NT file, maybe properties on a directory
entry. We would have to define a new TargetDataAttribute field, then put
the parent Object name in TargetDataObject, and so on. The benefit would
be that a query looking for everything that happened to a particular
data object would be a little easier, and would capture creation of that
object and setting its attributes with a single filter expression.

On the other hand, the TargetDataAttribute field will likely almost
always be null.

What do you all think? Does it make more sense to present
attributes/properties as something fundamentally different from
objects/files/tables, etc?

What about a column name in a DB? Would it fall under this new kind of
data container?


--
DCorlette
------------------------------------------------------------------------
DCorlette's Profile: http://forums.novell.com/member.php?userid=4437
View this thread: http://forums.novell.com/showthread.php?t=419794

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.