Hello!
In a table schema of mine I have:
__PACKAGE__-inflate_column('published', {
inflate = sub { time_db2obj(shift) },
deflate = sub { time_obj2db(shift) },
});
I noticed that the deflate method is NOT called when I use update() on a
resultset an pass data like this:
Matt S Trout wrote:
Richard Jolly wrote:
Hi,
DBIx::Class::AlwaysRS was on my list of things to get around to looking
at. Now it seems to be only available on backpan, though it is still
mentioned in the POD of ResultSetManager and Schema::Loader. Searches of
the catalyst and dbic mailing
Will Hawes wrote:
I'd vote for removing wantarray() completely. IMO, if a user wants
objects rather than a ResultSet, they should call -all.
How about providing *_all methods to avoid doubling the number of method
invocations and avoid constructing/destroying unwanted iterators?
Cheers, Dave
On 3/22/06, Vsevolod (Simon) Ilyushchenko [EMAIL PROTECTED] wrote:
Hi,
With Brandon's help, I've created a simple example that uses
Schema::Loader, but I've hit a snag when I tried to use has_many.
First, the loader was created in the file Test/Schema.pm, and my model
classes were in
On 3/22/06, Jason Kohles [EMAIL PROTECTED] wrote:
On 3/22/06, Vsevolod (Simon) Ilyushchenko [EMAIL PROTECTED] wrote:
Hi,
With Brandon's help, I've created a simple example that uses
Schema::Loader, but I've hit a snag when I tried to use has_many.
First, the loader was created in the
Hi,
I'm currently using Class::DBI in some larger web applications and watching
this list. I've been playing around a bit with it (0.0499) and now have two
questions:
What is the preferred way to have DBIx::Class to run with mod_perl ?
With CDBI I use the solution described here:
Date: Wed, 22 Mar 2006 11:08:59 -0600
From: Brandon Black [EMAIL PROTECTED]
Subject: Re: [Dbix-class] DBIx::Class and mod_perl
To: dbix-class@lists.rawmode.org
On 3/22/06, Rolf Schaufelberger [EMAIL PROTECTED] wrote:
What is the preferred way to have DBIx::Class to run with
Dave Howorth wrote:
Will Hawes wrote:
I'd vote for removing wantarray() completely. IMO, if a user wants
objects rather than a ResultSet, they should call -all.
How about providing *_all methods to avoid doubling the number of method
invocations and avoid constructing/destroying unwanted