On 2/26/06, Scott Webster Wood <[EMAIL PROTECTED]> wrote:
> OK, I think I asked something along these lines before, but I am actually
> starting to code so I wanted to revise the question(s) a bit. I am looking
> for
> a good way to keep an up-to-date database (or perhaps use an XML-RPC/SOAP
> b
On 2/13/06, Tim Bunce <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 13, 2006 at 02:03:22PM -0800, Ben Tilly wrote:
> > What $VERSION was this implemented at?
>
> I didn't say it was for sure. Just that I intended it and thought it was.
> Now I look at the code I see it&#x
->trace($level, $filehandle) works now so I think you can
> used a tied filehandle - certainly that's my intention.
>
> Then the PRINT method of your tied filehandle class can do whatever you
> want.
>
> Tim.
>
> On Fri, Feb 10, 2006 at 08:55:30PM -0800, Ben Tilly wr
think you can
> used a tied filehandle - certainly that's my intention.
>
> Then the PRINT method of your tied filehandle class can do whatever you
> want.
>
> Tim.
>
> On Fri, Feb 10, 2006 at 08:55:30PM -0800, Ben Tilly wrote:
> > Is there any easy way of reformatting tra
Is there any easy way of reformatting trace information?
I'd like a trace exactly like what DBI->trace(2) creates, except that
I'd like the timestamp (as precise as possible) and pid (ie $$) to be
included in the trace.
So far the best solution that I can think of is to create a named pipe
per pr
