[Bioperl-l] RE: bioperl-db - changes (Chris Mungall)

[Chris Mungall]

OOPS!!!

It turns out I was using the correct cvs branch (default == HEAD), I had
just neglected to check for any warning messages after saving my commit
message! Sure enough, my changes never went through do to a conflict.

Ok, they're really in there this time (may take a wee while to propagate
to webcvs)

On Tue, 12 Feb 2002, Brian Desany wrote:

> I don't see these changes when I do "cvs -n -q update" or "cvs status" or go
> to WebCVS - is there normally some kind of a delay or is there some other
> cvs command I need to use to find out which files have been changed? Do I
> need to specify a particular branch maybe?
> 
> Thanks,
> -Brian.
> 
> >
> > I have committed some code to bioperl-db
> >
> > * Fuzzy Locations are now handled, using the location_qualifier_value
> > table added to the biosql-schema during the hackathon.
> >
> > * Optimisations - all the features and locations for a
> > sequence entry are
> > now fetched in a few SQL calls rather than a number of calls
> > proportional
> > to the number of features.
> >
> > * Tidying - a lot of mysqlisms removed or pushed up to the BaseAdaptor
> > layer, to allow for easier postgres support. Added a few
> > generic ease of
> > use methods to BaseAdaptor to more clearly expose the logic in the
> > individual adaptor layer.
> >
> > * DBTestHarness now no longer uses the copy of the schema in the
> > bioperl-db directory. Instead it checks
> > ../biosql-schema/sql/biosqldb-mysql.sql - hmmm, this won't
> > necessarily fit
> > with the cvs re-organisation. How should we do this? An env
> > var seems a
> > bit nasty.
> >
> > ---
> > Chris
> >
> 
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l@bioperl.org
> http://bioperl.org/mailman/listinfo/bioperl-l
>