daily usage report

[Alan DeKok]

On Aug 19, 2018, at 9:06 AM, Nathan Ward <lists+freeradius at daork.net> wrote:
> 
>> Mangling existing tables && procedures is almost always the wrong idea.
> 
> I agree generally. I think my solution - to add a new trigger but not changing existing SQL, is a pretty good compromise. It’s not perfectly clean, but, it’s pretty close.

  Yes.

  TBH, the most efficient solution would be to put all of the SQL module logic into a stored procedure.

  i.e. instead of doing query1 INSERT, nope... query2 UPDATE, etc.  Just do it all in a stored procedure.  It should be faster and more efficient.

  Then any subsequent roll-up of daily data can be done once a day, in that stored procedure.

  The sad point is that the embedded SQL languages are terribly complex.  So people just avoid them.

  Alan DeKok.