Databases
StackOverflow2013
Postsdbo
POParsing A String - Is There A More Efficient Method than Checking Each Line?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POParsing A String - Is There A More Efficient Method than Checking Each Line?
    primarykey
    data
    text
    <p>I am working on a project to parse out a text file. The file is output from networking equipment. The incoming string is anywhere from a few thousand to tens of thousands of lines long. There will be a variable number of entries with keywords like these:</p> <pre><code>fcN/N is up Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN) Port WWN is 20:52:00:0d:ec:ef:b0:40 Admin port mode is F, trunk mode is on snmp link state traps are enabled Port vsan is 10 fcipN is up ..... port-channel-N is trunking ...... </code></pre> <p>The N is a number. There will always be the 'fcN/N' entries, there may or may not be the other two. The 'fcip' and 'port-channel' entries will have similar status information after each one as the fcN/N entries. All entries of the same type will be grouped - there won't be an fc followed by an fcip followed by another fc. Also as a general rule, all the fc entries are listed, then all the port-channel then all the fcip but I don't want to assume that. At the moment I have about 7 different RegEx patterns I am looking for. I do this by examining each line in turn, however managing all those is cumbersome. I thought about splitting the string on newline and then some kind of LINQ select to get all of each of the 3 types of entries, but that assumes they are always grouped in the same order. I also thought about 3 monster regexes to match everything from one entry to the next, but my experience is those are tough to get working and almost unreadable. Another thing I thought of was first match the three keywords - fc or port-channel or fcip, then have an if statement that matches the patterns unique to those. That is still matching each line for all 3 patterns though.</p> <p>To be clear, I have the Regex patterns working. I am looking for a more efficient way to do this than test each line for 6 0r 8 matches.</p> <p>Any other ideas? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAdi Lester
    1. USDavid Green
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POParsing A String - Is There A More Efficient Method than Checking Each Line?
      1. USDouglas
      1. VTFavorite
    2. VO
      singulars
      1. POParsing A String - Is There A More Efficient Method than Checking Each Line?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POParsing A String - Is There A More Efficient Method than Checking Each Line?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you experience performance issues right now? Are the Regex compiled?
      singulars
      1. POParsing A String - Is There A More Efficient Method than Checking Each Line?
      1. USDamien
    2. CONo. I am just looking for a more elegant way than brute-force. There may not be a more elegant way and I am cool with that. :) I didn't know you could compile a Regex, not sure what that means.
      singulars
      1. POParsing A String - Is There A More Efficient Method than Checking Each Line?
      1. USDavid Green
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload