[BioSQL-l] State of BioSql?

[Hilmar Lapp]

Thanks Peter. David - not much I can add to that other than that an only very slowly changing schema can be a desirable thing if stability matters and the schema mostly fulfills your needs.

If you want to be sure about the maturity of the support in Bioruby, I'd email the Bioruby developer list. My recollection is that it works well.

-hilmar

Sent with a tap.

On Sep 18, 2012, at 12:19 PM, Peter Cock <p.j.a.cock at googlemail.com> wrote:

> On Tue, Sep 18, 2012 at 6:58 PM, David Wilbur <wildboar at workwerks.com> wrote:
>> Hi,
>> 
>> i am working on a project that sees potential uses for BioSql. (which
>> we would be, if chosen, using with a current version of ruby, bioruby,
>> rails and postgres)
>> 
>> i am mostly interested in the state of the project, it appears to have
>> no changes since 2008.
> 
> No releases of BioSQL itself for a while I grant you, but the most recent
> change was last week https://github.com/biosql/biosql/commits/master
> (an update for the MySQL schema), and a year ago an SQLite schema
> was added.
> 
> I'd like to see another point release (to ship the SQLite schema) but
> it needs someone with Perl expertise to update the misc BioSQL
> Perl scripts. Adding support for BioSQL on SQLite to BioPerl etc
> would also be great (currently only available in Biopython I think).
> 
> When you say no changes since 2008 are you talking about a
> particular Bio* binding for BioSQL?
> 
>> ruby, bioruby, and postgres, have both changed a lot since that time.
>> eg: http://lists.open-bio.org/pipermail/biosql-l/2011-November/001795.html
>> has this better solution for transactions been worked on? and so on...
> 
> Good question - Biopython has some special case code to cope
> under PostrgreSQL with and without those special case rules
> needed under BioPerl.
> 
> Peter
> _______________________________________________
> BioSQL-l mailing list
> BioSQL-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/biosql-l