[ome-devel] New Branch for DB Updates

[Jason Swedlow]

Hi-

This all sounds fine-- a few comments.

1) Adding these changes in, along with all the other recent updates 
adds up to alot of structural changes on the server.  We have been 
running a recent version of HEAD on one of our servers here-- let us 
assess how well that has been tested and then get back to you.  Give us 
a few days, hopefully end of week.

2) The updated version of screening model has been bounced around many 
screeners, and is now in my lap, waiting final modifications to 
documentation.  Will try to get this out to the list later today.  This 
certainly should go in, once it is agreed.

Cheers,

Jason


On 16 May 2005, at 17:07, Ilya Goldberg wrote:

> Hi all
> Some of you monitoring the CVS RSS feed may have noticed that I 
> started a branch (OME_2_4_1_DB_UPDATES) to deal with DB updates that 
> have been on deck for a while.  As mentioned before, the proposed 
> updates were these:
>
> 1. Change CONFIGURATION.VALUE to type text (bug 460).
> 2. Change ST FilenamePattern.Basename to text to allow storing comma 
> separated values rather than integer (to get the full basename from 
> several RE 'parts').  Requested by Nico Stuurman to support his 
> filename naming scheme from a Beckman screening scope (Bug 484)
> 3. Add group owner to MODULE_EXECUTIONS, fix bug 469 (attribute 
> ownership inherits from MEX)
> 4. Not NULL constraint on attribute's MEX column (bug 485).
> 5. Not NULL constraint on MEX experimenter column (bug 468).
> 6. ST foreign key constraints for references (PKs already declared) 
> (Bug 486).
> 7. ST constraints (not NULL, specifically) (Bug 393)
> 8. Normalize "Plane" and "Stack" STs (i.e. finalize data model).  Use 
> a reference to it for PlaneStatistics.  Do the same for "Stack" ST.  
> When this is done, convert plane/stack stats to class-per-table.  
> Clean up back-end code that deals with non-class-per-table.  Consider 
> eliminating table/column specification from STs by adopting a 
> table/column naming convention.
> 9. USER_STATE => key-value (like CONFIGURATION).  New table with 
> session_id referring to OME_SESSIONS?  If so, remove extra columns 
> from OME_SESSIONS.
>
> The branch (OME_2_4_1_DB_UPDATES) implements the first five of these.  
> Please indicate wether there is interest in implementing the rest.  
> I'm pretty sure that I will at least implement #6 (Bug 486).  The 
> update scripts in this branch will update a 2.2.0 and 2.4.0 DB to 
> version 2.16.
>
> There was a proposal for plate/well/screen modifications.  Any chance 
> that this can be distilled to a series of table/column modifications 
> or at the very least, ST declarations in XML?  These can be placed 
> right in the OME_2_4_1_DB_UPDATES branch.
>
> To checkout the branch (its the entire OME CVS module),
> cvs co -r OME_2_4_1_DB_UPDATES OME
>
> It would be ideal if we could re-merge this branch with HEAD as soon 
> as possible.
>
> -Ilya
>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>
>

NOTE NEW EMAIL ADDRESS: jason at lifesci.dundee.ac.uk
**************************
MSI/WTB Complex
The University of Dundee
Dow Street
Dundee  DD1 5EH
United Kingdom

phone (01382) 345819
Intl phone:  44 1382 345819
FAX   (01382) 348072
email: jason at lifesci.dundee.ac.uk

Lab Page: http://www.dundee.ac.uk/lifesciences/swedlow/
Open Microscopy Environment: http://www.openmicroscopy.org
**************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 3621 bytes
Desc: not available
Url : http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20050517/866cd215/attachment.bin