Re: Accounting and Acct-Delay-Time in MySQL

2010-12-02 Thread Alan DeKok
Stefan Winter wrote: Okay, I'll see what I can do. One thing I noticed is that the default schema has a column xascendsessionsvrkey varchar(10) default NULL, A VSA, of a vendor that's long dead? This is one column that I would wipe out. If some people find they need it, they can always

Re: Accounting and Acct-Delay-Time in MySQL

2010-12-02 Thread Phil Mayers
On 18/11/10 07:58, Stefan Winter wrote: Hi, I'd re-visit the entire accounting table queries. Create a *new* table, so that people don't have surprises when they upgrade. Ideally, it should be robust in the face of duplicate packets, and packets forwarded via 2 different paths

Re: Accounting and Acct-Delay-Time in MySQL

2010-11-18 Thread Stefan Winter
Hi, I'd re-visit the entire accounting table queries. Create a *new* table, so that people don't have surprises when they upgrade. Ideally, it should be robust in the face of duplicate packets, and packets forwarded via 2 different paths (think radrelay + delays) Okay, I'll see what

Re: Accounting and Acct-Delay-Time in MySQL

2010-11-17 Thread Alan DeKok
Stefan Winter wrote: the default queries for mysql log Acct-Delay-Time into the columns acctstartdelay and acctstopdelay, respectively. They leave the timestamps for acctstarttime and acctstoptime at %S. For a non-zero delay, this means that a database reader needs to do math to get the

Accounting and Acct-Delay-Time in MySQL

2010-11-15 Thread Stefan Winter
Hello, the default queries for mysql log Acct-Delay-Time into the columns acctstartdelay and acctstopdelay, respectively. They leave the timestamps for acctstarttime and acctstoptime at %S. For a non-zero delay, this means that a database reader needs to do math to get the start and stop