Bob MacCallum wrote: > Interesting stuff - we will try to give the beta a try ASAP. > > What's the general strategy behind the provision of storage of array designs > and data as files rather than in the db? Some reasons I could think of: > > Is it to handle arbitrary future array technologies without tying up core > developer time? > > Is it to handle future array designs with too many features for mysql/postgres > to handle?
The original use case is the Affymetrix case, which has too many probes on an array design. Since downstream analysis still wanted the CDF/CEL files there was no real benefit from importing everything to the database. As I understand it the future brings arrays with a larger number of spots/features where the same arguments can be applied. There is for example already the Illumina platform where "beads" are just randomly distributed on the arrays. There is no such thing as an array design in the original sense that everything can be positioned with block, row and column coordinates. The main reason is that now BASE can really support any type of data. At least for storage. To be able to do anything with the data additional code/plug-ins has to be developed. I think it is a good thing that this can now be developed externally. This should now be easier than before since everything that needed special handling for Affymetrix has now been made pluggable. /Nicklas ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ basedb-devel mailing list basedb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/basedb-devel
