bret at pectopah
Sep 8, 2009, 9:51 AM
Post #2 of 3
This has been remedied in newer Bricolages with an extra database index.
See this thread for an explanation of how it works:
Hope this helps,
On Tue, 2009-09-08 at 17:43 +0100, David Oliveira wrote:
> I have a problem with story versioning.
> When a story is changed and published, it generates a new version of
> the story.
> A story with an high version number (about 2000+), becomes too slow
> getting, searching and operating on it.
> If we have more stories with this characteristics, the speed problem
> is multiplied by the number of stories.
> Tipically I solve this by cloning the story to another but anyway,
> this is not a solution.
> Is there a way for clearing story versions or something to avoid this
> Thank you.
> David Oliveira
> <d.oliveira [at] prozone>
Pectopah Productions Inc.
bret [at] pectopah