On 6/22/07, Michael Lackhoff <[EMAIL PROTECTED]> wrote:
> Thanks for the hint! This almost did it. Some tests showed that I had
> to use the connection-variant of pnotes in my setup:
>
> use Apache2::ConnectionUtil;
> # grab the connection object;
> my $c = $r->connection;
You really shouldn't nee
On 6/22/07, Michael Lackhoff <[EMAIL PROTECTED]> wrote:
> I didn't get a result. Within the authentication handler I stuffed an
> object (or even a simple string) into $r->pnotes and tried to write it
> to the logfile from the authorization handler but it was empty, the
> same test worked with $c->
On 22 Jun 2007 at 10:03, Perrin Harkins wrote:
> On 6/22/07, Michael Lackhoff <[EMAIL PROTECTED]> wrote:
> > Thanks for the hint! This almost did it. Some tests showed that I had
> > to use the connection-variant of pnotes in my setup:
> >
> > use Apache2::ConnectionUtil;
> > # grab the connection
On 6/22/07, Svilen Ivanov <[EMAIL PROTECTED]> wrote:
> This serialized columns seem common practice (at least 2-3 devs asked
> up till now) but inclusion in RDBO package may be overkill, how about
> posting the samples in documentation or in the wiki (I faintly recall
> RDBO wiki somewhere)?
There
Basic question.
As with all database work, when I write a report, sometimes I need to show a
column which is not a field but is calculated on the fly from fields in the
database.
Does Rose facilitate such "display-only" fields in some way?
Thought it was worth asking if there was a "correct" way
On Jun 22, 2007, at 6:27 PM, James Masters wrote:
> Basic question.
> As with all database work, when I write a report, sometimes I need
> to show a
> column which is not a field but is calculated on the fly from
> fields in the
> database.
>
> Does Rose facilitate such "display-only" fields
