Hi I also saw this; The DB has to be fixed since this effects when one tries to read data, not to write new ones. Thus it does not help to change production version. There are already files with prduction version 2. Flemming Subject: Re: [Brahms-dev-l] filecatalogue problem > Hello. The problem is not your script. It is in the database. Someone > recently has added new gtr production version (#2) for run period 3 > despite the fact that there exits already the gtr production version 2 > for the same data set. (I know it is the most recent production entry > since it has the higherst version id.) Therefore, query to our database > will fail. (I guess that user was not carefull and the web interface > did not have check for dumb mistake.) Anyway, the easiest way is to > change this production version to be 3 (not 2). Then, your problem will > disappear. Is this what you (whoever added new version) want? > > Hiro > _______________________________________________ > Brahms-dev-l mailing list > Brahms-dev-l@lists.bnl.gov > http://lists.bnl.gov/mailman/listinfo/brahms-dev-l > _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Wed Nov 30 08:08:09 2005
This archive was generated by hypermail 2.1.8 : Wed Nov 30 2005 - 08:08:13 EST