On 12/29/06 8:57 PM, Jonathan Vanasco wrote:
> On Dec 29, 2006, at 7:53 PM, John Siracusa wrote:
>> If you jut want the value of now() in isolation, plain DBI is the way to go.
>> (Wrap the code in a function or class method somewhere to hide the gory DBI
>> details.)
>>
> the problem I see is t
On Dec 29, 2006, at 7:53 PM, John Siracusa wrote:
> If you jut want the value of now() in isolation, plain DBI is the
> way to go.
> (Wrap the code in a function or class method somewhere to hide the
> gory DBI
> details.)
the problem I see is that you can run into issues where NOW() is
tra
On 12/29/06 7:25 PM, Jeffrey Horn wrote:
> I need to get the value of Now() from the database server (as opposed to the
> server on which my perl script is running) and wanted to know if there is a
> quick and elegant way to get that value in a Rose-y way (as opposed to
> dropping down to DBI). Ju
At 6:25 PM -0600 12/29/06, Jeffrey Horn wrote:
>I need to get the value of Now() from the database server (as opposed to the
>server on which my perl script is running) and wanted to know if there is a
>quick and elegant way to get that value in a Rose-y way (as opposed to
>dropping down to DBI).
I need to get the value of Now() from the database server (as opposed to the
server on which my perl script is running) and wanted to know if there is a
quick and elegant way to get that value in a Rose-y way (as opposed to
dropping down to DBI). Just want to make sure I haven't missed such a
feat
