On 20/10/10 18:40, Hetényi Csaba wrote:
The automatic schema generation is a very convenient feature -especially
in developing phase, when table structures often change.
I hear you!... I have the exact same issue.
So far writing my own script that harnesses the power of
I have a Catalyst model that runs a system command as part of a search
facility. The system call only takes a fraction of a second so is processed
inline and this all works fine when tested outside of Catalyst and when
called under the Catalyst standalone server. However, when I deploy it to my
You may want to check your version of FCGI. There are previous reports
of related issues, which seem to be an interaction between IPC::*
modules expectations of standard input/output/error, and FCGI, which
fakes them. See
http://www.mail-archive.com/po...@openbsd.org/msg16948.html for an
I've run into this problem with FCGI too. Our solution at the time, since the
fileno call was in an internal API, was to skip it when STDOUT was tied.
Getting an updated FCGI instead sounds like a happier thing.
I notice this in current FCGI comments:
# Some things (e.g. IPC::Run) use fileno
heidi brandenburg wrote on 10/21/2010 03:02 PM:
I've run into this problem with FCGI too. Our solution at the time, since the
fileno call was in an internal API, was to skip it when STDOUT was tied.
Getting an updated FCGI instead sounds like a happier thing.
I notice this in current FCGI
On 22 October 2010 05:43, Ian Sillitoe i...@sillit.com wrote:
I have a Catalyst model that runs a system command as part of a search
facility. The system call only takes a fraction of a second so is processed
inline and this all works fine when tested outside of Catalyst and when
called under
