Yes we use sql only for accounting. We will try decoupled accounting then.
There are some complex problems on our DB, the team and DBA are working
on it too.Thank you for the advice.
Thank you all for your help :)
Nakamura
> On Tue, Apr 2, 2013 at 9:13 AM, Mitsuhiro Nakamura <[hidden email]>
On Tue, Apr 2, 2013 at 9:13 AM, Mitsuhiro Nakamura wrote:
>
> Alan,
>
> Thank you.
> Our database has some problem and the response is slow.
> Since the problem itself seems to take long time to fix it, we wanted to
> avoid it.
>
>
Are you using sql ONLY for accounting?
If yes, then Olivier's s
On 2 avr. 2013, at 04:13, Mitsuhiro Nakamura wrote:
>
> Alan,
>
> Thank you.
> Our database has some problem and the response is slow.
> Since the problem itself seems to take long time to fix it, we wanted to
> avoid it.
Look at the decoupled accounting virtual server example.
Olivier
-
Lis
Alan,
Thank you.
Our database has some problem and the response is slow.
Since the problem itself seems to take long time to fix it, we wanted to
avoid it.
If there is no way to do, then we will try to find the otherway.
Regards,
Nakamura
>
>
> Mitsuhiro Nakamura wrote:
> > When using rlm_sq
Mitsuhiro Nakamura wrote:
> When using rlm_sql, it always wait for response from database.
That's how it works.
> Is there any way to configure to avoid it?
> (We don't wanna wait for its result after prosessing)
Why?
> accounting {
> detail
> sql <-wish to prosess it he
Hi all,
When using rlm_sql, it always wait for response from database.
Is there any way to configure to avoid it?
(We don't wanna wait for its result after prosessing)
accounting {
detail
sql <-wish to prosess it here without waiting for result
}
We'd appreciate if anyone ca
6 matches
Mail list logo
