Re: Gathering package upstream meta-data in the UDD. (was: Re: more formally indicating the registration URL)
On Tue, Jan 19, 2010 at 10:51:48PM +0900, Charles Plessy wrote:
> Are you sure we need a primary key??? For instance, to retreive a publication
> year, I have the impression that the following paraphrasing the python code of
> blends??? blendstasktools.py would be enough:
No, forget it - I missinterpreted your previous mail.
> With a table like:
>
> CREATE TABLE "biblio" (package, key, value);
> INSERT INTO "bib" VALUES('kalign','DOI','10.1093/nar/gkn1006');
> INSERT INTO "bib" VALUES('seaview','DOI','10.1093/molbev/msp259');
> INSERT INTO "bib" VALUES('ballview','DOI','10.1093/bioinformatics/bti818');
> INSERT INTO "bib" VALUES('kalign','PMID','19103665');
> INSERT INTO "bib" VALUES('seaview','PMID','19854763');
> INSERT INTO "bib" VALUES('ballview','Reference-Year','2006');
> INSERT INTO "bib" VALUES('kalign','Reference-Year','2009');
> INSERT INTO "bib" VALUES('seaview','Reference-Year','2009');
>
> Note that this is the first time I deal with Python code, so please be indulgent :)
I perfectly understand your intention now and I this is fine for me.
However, I wonder if we should use an additional table mentioning the
keys we are actually using. When I write database applications I just
do this to make sure no invalid values will propagate into the database
- but perhaps this is overkill here and consumes resources of the server
for not much use.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: