Re: [Bodington-developers] Wtd: Expertise on uploaded_files table structure

[Colin T. <col...@ou...>]

Jon Maber wrote:
> A change is needed urgently - removing the constraint would be the most 
> obvious first step. Was there a bug report that led to the addition of 
> the constraint? Is there another way round that bug?

Matthew would have to answer that. We had a lot of problems with 
Uploaded File behaviour, most notably where they all disappear from the 
display periodically, and our uploaded files table got itself pretty 
messed up. Matthew rewrote large chunks of code to sort that out, and 
we've had very few bug reports (they were fixed).

There is a difference between our version of the index and that on Bod:

Ours has the following:

CREATE UNIQUE INDEX uploaded_files_unq_name ON uploaded_files 
(parent_uploaded_file_id, name)
GO

-- Only PostgreSQL supports partial indexes.
--CREATE UNIQUE INDEX  uploaded_files_one_root ON uploaded_files 
(resource_id )
--	WHERE parent_uploaded_file_id IS NULL
--GO


Colin

-- 
____________________________________
Colin Tatham
VLE Team
Oxford University Computing Services

http://www.oucs.ox.ac.uk/ltg/vle/
http://bodington.org