Opened 18 years ago
Last modified 10 years ago
#1036 new bug
Tracker Doesn't Like Hard Links
Reported by: | bonefish | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | Unscheduled |
Component: | Applications/Tracker | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Tracker has a few issues with respect to hard links, apparently because it doesn't distinguish between nodes and entries consequently enough. The following observation were made under BeOS R5:
- In a Tracker window displaying a directory that contains several entries referring to the same node, only one of those entries is displayed, the others are missing.
- Similarly to the first point, a query window displaying entries only lists one entry per node, even if the responsible file system reported more than one entry for the node.
- A B_ENTRY_REMOVED live query notification will remove the node (i.e. the one entry displayed for it) from the query window, even if other entries referring to the node did and still do belong to the query result set (and were correctly reported by the responsible file system)
Change History (3)
comment:1 by , 18 years ago
comment:3 by , 10 years ago
Priority: | normal → low |
---|---|
Version: | R1/pre-alpha1 → R1/Development |
Still applies. Some workarounds have been put in places in other applications though.
Note:
See TracTickets
for help on using tickets.
I suppose some Pose lists are keyed by node_ref rather than entry_ref because it's faster since it doesn't include a string...