On 19.07.2009 17:14 Uhr, Alex Balashov wrote:
Very strange mystery. Needless to say I cannot reproduce this on K 1.5.x proper.
It is specific for devel version, probably introduced when DB initialization was reshaped because of the new PROC_INIT rank. Should be fixed now in git.
Also, while I cannot comment on this deeply as I am not on the receiving end of bug requests, it has not been my impression that the dialog module is so buggy. Apart from the crashes I reported in the initial 1.5.0 release that were promptly resolved, I have not had any problems with it, and have been using it with great success in fairly high-volume production environments with K 1.5.1 and beyond.
I do use it in several deployments without any issue.
Cheers, Daniel
Alex Balashov writes:
What'd you set db_mode to?
i didn't set it so anything:
5.10. db_mode (integer)
...
Default value is ??0??.
-- juha