I am not sure I can do this. I will try to look into the code and see. In case
I have good news I will come back.
On December 17, 2016 5:45:10 PM EET, Paolo Lucente <pa...@pmacct.net> wrote:
>Nope, this is still on the todo list and was over-taken by other
>priorities in the space of BGP, BMP, Streaming Telemetry and support of
>Apache Avro. This is still of interesest though. Would you be able to
>help yourself with the code development?
>On Thu, Dec 15, 2016 at 01:08:01AM +0200, rightkicktech.gmail.com
>> Hi Paolo,
>> It has been mentioned that ndpi was in the todo list to provide an
>alternate way of classifying traffic on layer 7. Can pmacct 1.6.1 yet
>integrate with ndpi?
>> On December 13, 2016 6:55:43 PM EET, "Karl O. Pinc" <k...@meme.com>
>> >On Tue, 13 Dec 2016 15:05:31 +0000
>> >"Miethe, Martin" <mie...@studentenwerk-leipzig.de> wrote:
>> >> I just spent some time trying to set up dynamic mysql tables. The
>> >> keeps saying:
>> >> Dec 13 15:26:01 INFO ( out/mysql ): *** Purging cache - START
>> >> 20506) *** Dec 13 15:26:01 ERROR ( out/mysql ): PRIMARY 'mysql'
>> >> backend trouble. Dec 13 15:26:01 ERROR ( out/mysql ): The SQL
>> >> says: Table 'pmacct.acct_out_20161213-1525' doesn't exist
>> >> The table 'pmacct.acct_out_20161213-1525' definitly exists -
>> >> did succesfully create it using the sql_table_schema from my
>> >> After some debugging I found that the problem is the "-" sign I am
>> >> using for my table names, as it is considered as a special
>> >> for mysql. To use special characters in mysql you need to use the
>> >> quote character - the backtick.
>> >> Its not a problem for me to go without these characters and its
>> >> probably not a good practice to use them in first place. But still
>> >> maybe its worth thinking about to wrap the dynamic sql statements
>> >> generation into backticks to get around this problem if someone
>> >> to use such characters?
>> >This is something that needs real thought put into it. For example,
>> >the SQL working draft of the 2003 Standard (which happens to be what
>> >I can get my hands on to easily without paying)
>> >ISO/IEC 9075-2:2003 (E)
>> >(ISO-ANSI Working Draft) Foundation (SQL/Foundation)
>> >5.2 <token> and <separator>
>> >page 134
>> >says that the double quote character is supposed to be used to quote
>> >identifiers, not the backtick. So MySQL is "special" in this
>> >(And others. MySQL brings out the cranky in me. :)
>> >I don't know what SQL 2011 says.
>> >In PostgreSQL you do use double quotes to quote identifiers
>> >special characters. When you do so (and according to the SQL
>> >the result is case-sensitive. But when you don't it's
>> >The PG docs say that PG is non-SQL conformant in that unquoted
>> >identifiers are folded to lower case, but the standard says that
>> >they should be folded to upper case.
>> >In any event, indiscriminately quoting identifiers will lead to
>> >case-insensitivity, or it should. This can break existing setups.
>> >My inclination is to leave well enough alone. The SQL standard
>> >is bad, allowing myriad variations, and SQL implementations are
>> >introducing yet more non-standard inconsistencies. If there's a
>> >reason to get involved with SQL details that would be one thing, but
>> >going there without a good reason sounds like trouble. Let the
>> >using the various databases deal with the weirdness themselves.
>> >All that said, wouldn't hurt to add some note regards the generated
>> >syntax somewhere in the docs. Martin, if you have any suggestions
>> >along these lines I'm sure Paolo would be happy to consider them.
>> >Karl <k...@meme.com>
>> >Free Software: "You don't pay back, you pay forward."
>> > -- Robert A. Heinlein
>> >pmacct-discussion mailing list
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> pmacct-discussion mailing list
>pmacct-discussion mailing list
Sent from my Android device with K-9 Mail. Please excuse my brevity.
pmacct-discussion mailing list