Re: Read-only root database doesn't work ... bug or feature?
On Fri, May 21, 2004 at 03:09:48PM -0400, Tres Seaver wrote:
Paul Winkler wrote: (snip)
I have not yet found exactly how Formulator triggers a commit, but it is definitely something called by its initialize() function.
It is probably trying to do the Right Thing (TM) by registering with the help system. The fact that the help system writes to the database is a wart the size of my foot.
Good thought, but practically everything else does that too, and Formulator's the only one that triggers this issue. I've tracked it further to Formulator.FieldRegistry.initializeFieldForm() but I don't grok what that's doing yet, only just started looking at it... -- Paul Winkler http://www.slinkp.com
On Fri, May 21, 2004 at 03:59:21PM -0400, Paul Winkler wrote:
On Fri, May 21, 2004 at 03:09:48PM -0400, Tres Seaver wrote:
Paul Winkler wrote: (snip)
I have not yet found exactly how Formulator triggers a commit, but it is definitely something called by its initialize() function.
It is probably trying to do the Right Thing (TM) by registering with the help system. The fact that the help system writes to the database is a wart the size of my foot.
Good thought, but practically everything else does that too, and Formulator's the only one that triggers this issue.
I've tracked it further to Formulator.FieldRegistry.initializeFieldForm() but I don't grok what that's doing yet, only just started looking at it...
OK, it creates three instances of Formulator.Form.BasicForm, which is persistent; and it writes to all three. I don't really grok why these three need to be persistent, that smells funny since these are recreated on every restart. I'll take it up with the author. Thanks everybody. -- Paul Winkler http://www.slinkp.com
participants (1)
-
Paul Winkler