comments, dumping, and adding

[markito3]

Subject: | Re: analysis currently broken
Fri, 26 Oct 2018 18:56:39 -0400 (EDT)
Alexander Somov somov@jlab.org
David Lawrence davidl@jlab.org
Beni Zihlmann zihlmann@jlab.org, Mark M. Ito marki@jlab.org, Simon Taylor staylor@jlab.org

Hi,

Simon has just found the problem:

When one dumps the table from the DB (in order to modify/add fields),
the "dump" command does not inhibit # tags, such as

#Restore slot,channel for TAGM column 19, new slot,channel for TAGM

This line(s) has to be removed by hand when you "add" the
modified table.

--

There are no error messages when you "add" a table containing
non-xml tags. I think that we need to ask Dmitry to modify
the "dump" command and "suppress" non-xml characters

All in all, the problem seems to be fixed now (I modified the table)

Cheers,
Sasha

[DraTeots]

It would be very good to have exact commands, that do this (with table names) with our HallD db. Like:

> dump xxx/yyy
> add ...
# and now we have a problem

[markito3]

I tried and cannot reproduce the problem. It could be that my test case did not address the alleged bug. Could someone provide an example per @DraTeots request, perhaps @somovalex or @staylorjlab?

[staylorjlab]

The problem is specific to the translation table (xml) at the parsing stage because the "#" symbol outside of < /> is not valid xml and this does not impact other tables where the comment character "#" is harmless.

[sdobbs]

For tables which contain string data, I've always just used dedicated python scripts to add in the information. We should either have a policy about this, or perhaps some special mode (switch) for the command line program is needed. On Thu, Nov 1, 2018 at 7:52 AM staylorjlab <notifications@github.com<mailto:notifications@github.com>> wrote: The problem is specific to the translation table (xml) at the parsing stage because the "#" symbol outside of < /> is not valid xml and this does not impact other tables where the comment character "#" is harmless. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#58 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABIJavuu4uFlOmLEQnsBKVWJ6qR5nXeSks5uquBygaJpZM4YCJhj>.