Work has finally begun in earnest on my log analyzer that I promised to work on "one day" back when I started to get into Marpa .
There's not much to see yet, aside from one work-in-progress "input config" file. Input config spec coming soon -- as soon as I've nailed down what input specs need to be capable of. One of the things it will need to be capable of is using Marpa-based parsers to grok log entries (as well as using simple regexes). I may also need to use Marpa to make the query language, which in turn might need me to work on an SQL::Translator module to convert generic SQL into the SQL needed to query the database of parsed logs. I plan to store it in SQLite (by default, but let the user choose), but SQLite lacks some of the features that I've grown to know & love that are present in Oracle, and that I want to have in my SQL dialect. https://github.com/PWBENNETT/perl-Gloria/tree/develop -- Paul W Bennett <div id="DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><table style="border-top: 1px solid #aaabb6; margin-top: 30px;"> <tr> <td style="width: 105px; padding-top: 15px;"> <a href="https://www.avast.com/sig-email" target="_blank"><img src="https://ipmcdn.avast.com/images/logo-avast-v1.png" style="width: 90px; height:33px;"/></a> </td> <td style="width: 470px; padding-top: 20px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">This email has been sent from a virus-free computer protected by Avast. <br /><a href="https://www.avast.com/sig-email" target="_blank" style="color: #4453ea;">www.avast.com</a> </td> </tr> </table><a href="#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div> -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
