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

[Matthew B. <mat...@ou...>]

Jon Maber wrote:
> The problem lies with the change to uploaded_files.sql which was checked 
> in 3 weeks ago. It adds this unique index;
> 
> CREATE UNIQUE INDEX uploaded_files_unq_name ON uploaded_files 
> (parent_uploaded_file_id, name)
> GO
> 
> This constraint is ok for files and sub folders because they all have a 
> parent_uploaded_file_id but the root folder for each resource has a null 
> parent_uploaded_file_id and always has the same name.  Consequently this 
> constraint is bound to  prevent  uploading of files to any new resource 
> other than the first resource that files were uploaded to since 
> installation.
> 
> 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?

The simple change is to remove the constraint as it was a belt a braces 
solution. Shall I remove them from the upgrade script and uploaded files 
SQL file?

-- 
  -- Matthew Buckett, VLE Developer
  -- Learning Technologies Group, Oxford University Computing Services
  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/