-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/26/07 13:37, Isaac Ben wrote: > On 1/26/07, Bruno Wolff III <bruno@xxxxxxxx> wrote: >> On Thu, Jan 25, 2007 at 10:47:50 -0700, Isaac Ben >> <ib.zero@xxxxxxxxx> wrote: [snip] > > I plan on accessing the data with postgres via python and R. The > main reason for putting the data in postgres is that postgres > handles large data sets well and it will allow me to pull subsets > easily if slowly. I wonder if sed/grep/awk (or, just perl) could rapidly do your row and column pre-filtering? >> If you do put this in postgres, it seems the two most natural >> things are to use arrays to store the dimension values or to >> have table with a key of the gene and the dimension and have >> another column with the value of that dimension for that gene. > > Yeah, I received a tip from someone regarding the use of arrays, > and I think that I will be using that. Thanks for the tips. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFulz7S9HxQb37XmcRArBQAKCZc1Eusg/HtsdMKs8A6z8MTT6FgACg1GuU yOjqrCxi8CIPX3rCjrDcX6U= =0xY2 -----END PGP SIGNATURE-----
