Re: [Openinteract-help] object_keys & object_track

[Chris W. <ch...@cw...>]

On Wed, 2002-08-21 at 03:50, And...@Be... wrote:
> looking at our oi database, we found that our object_keys table keeps
> filling, although we removed all object_track keys in the spops.perl files.
> So the assumption is, that we did not yet grasp the sense and function of
> object_keys and maybe also object_track.
> 
> Could anyone please "fill us in" ?

object_keys is entirely separate from object tracking. It was an
experiment used to abstract class + ID. Instead of having a class and ID
in every table which can refer to any other type of object -- full-text
index, etc. -- you stick the 32-character object_key in. I also got
tired of having to make the ID longer and longer in these tables, to
accommodate longer ID names mostly necessitated by the 'location' field
of HTML pages. (Mistake: I should have used a meaningless incrementing
ID and made 'location' unique. Ah well.)

I don't think this is necessarily a bad idea -- I think generic object
containers like the Everything2 Engine use something similar so you can
ask for a 'node_id' and get back a form, a poll, a discussion, etc. But
I think using a monotonically increasing ID would probably be a better
idea.

If you're not using object_keys for anything, then the only time it will
come into play is when you create an SPOPS object. If you'd like to stop
creating them, comment out the line:

  push @{ $rs_table->{post_save_action} }, \&save_object_key;

in OpenInteract::SPOPS->ruleset_factory.

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.