[BioSQL-l] Updates to biosql Oracle schema

Richard HOLLAND hollandr at gis.a-star.edu.sg
Mon Nov 15 20:26:15 EST 2004


Yes, 3000 is what we used. I think that particular value was obtained
from Len's schema - we have been using both yours and Len's in parallel
to see which works best for us.

Richard Holland
Bioinformatics Specialist
GIS extension 8199   
 
---------------------------------------------
This email is confidential and may be privileged. If you are not the
intended recipient, please delete it and notify us immediately. Please
do not copy or use it for any purpose, or disclose its content to any
other person. Thank you.
---------------------------------------------

> -----Original Message-----
> From: Hilmar Lapp [mailto:hlapp at gnf.org]
> Sent: Tuesday, November 16, 2004 9:25 AM
> To: Richard HOLLAND
> Cc: mark.schreiber at group.novartis.com; biosql-l at open-bio.org
> Subject: Re: [BioSQL-l] Updates to biosql Oracle schema
> 
> 
> On Nov 15, 2004, at 5:08 PM, Richard HOLLAND wrote:
> 
> > The column failing was bioentry_qualifer_value.value, which when
> > expanded to 300 characters in
> > length was able to store it. Not sure if this should be changed in
> > BioSQL or not?
> 
> I assume you mean 3000, not 300? In the DDL script the width is
> actually expanded to 4000, the full size. Also, if it's a translation
> then it will have been in the feature table, and the respective table
> would then be seqfeature_qualifier_value.
> 
> Apparently both column width expansions are in the DDL, but not in the
> migration script. I added them both to the migration script too
> (sql/biosql-ora/migrate/1.0/migrate-all.sql).
> 
> 	-hilmar
> --
> -------------------------------------------------------------
> Hilmar Lapp                            email: lapp at gnf.org
> GNF, San Diego, Ca. 92121              phone: +1-858-812-1757
> -------------------------------------------------------------




More information about the BioSQL-l mailing list