Hi Flemming et al, On Fri, 9 Nov 2001 21:25:46 -0500 "Flemming Videbaek" <videbaek@sgs1.hirg.bnl.gov> wrote concerning "Brahms DB access": > Having struggled today with some non-working root classes ... What other than what you told Kris and I? > The code is available for inspection (if you really want to) in > ~videbaek/newdb/brat, in particulary db/calib and db/abc. i think it > is fair to say that if this approach (or something very close to it) > is not agreed upon I will rest my case and let someone else carry > the torch. I just skimmed the code (db/abc/BrDb.cxx and db/calib/BrDbRevision.cxx), and it seems to that what you did, was to expand the Revision table to have another column, and then when you get the revision from the DB, or inserts the revision to the DB, you encode the into a string, specific for the data type. Ok, that looks fine to me (you know my reservations on this in the first place, so no need to recap). I just realised that we may not need to repopulate the revision table at all. I think we can do with a ALTER TABLE Revision ADD COLUMN datatype INT NOT NULL AFTER comment; [1] and then multiple UPDATE TABLE Revision SET datatype=<type> WHERE parameterId=<parameter>; This is ofcourse best done by hand or in a script. Yours, Christian Holm Christensen ------------------------------------------- Address: Sankt Hansgade 23, 1. th. Phone: (+45) 35 35 96 91 DK-2200 Copenhagen N Cell: (+45) 28 82 16 23 Denmark Office: (+45) 353 25 305 Email: cholm@nbi.dk Web: www.nbi.dk/~cholm [1] http://mirrors.sunsite.dk/mysql/doc/A/L/ALTER_TABLE.html
This archive was generated by hypermail 2b30 : Sat Nov 10 2001 - 09:17:22 EST