Forum OpenACS Development: Re: acs_objects_context_object_un

Error in include template "/var/www/openacs/packages/openacs-bootstrap3-theme/resources/templates/packages/forums/lib/search/search-form": can't read "form:id": no such variable
Collapse
2: Re: acs_objects_context_object_un (response to 1)
Posted by Dave Bauer on 06/14/06 02:55 PM
Malte,

What exactly would you change?

The unique constraint is because of an index on (context_id,object_id).

Or rather the other way around.

"
-- The unique constriant about will force create of this index...
-- create index acs_objects_context_object_idx onacs_objects (context_id, object_id);
"

Point is, we can't change this, and I can't imagine why you would want to. What sort of transactions are failing due to this constraint? An example would be helpful.

Collapse
3: Re: Re: acs_objects_context_object_un (response to 2)
Posted by Malte Sussdorff on 06/14/06 03:44 PM
The problem is described in https://openacs.org/forums/message-view?message%5fid=447214.

What I would change is to create the index and drop the unique constraint, as this seems to me to be the propper thing to do. But Dave explained that an index on (object_id,context_id) will create a unique constraint.

Now my question would be, why is that the case. But maybe I should ask over at postgresql. Any way how this could be detected? I mean if the database is creating a unique constraint, shouldn't this show up in \d ?