stephen joseph butler wrote:
If you want something one line, how about this:
my $vote = $foo ? $bar : undef;
Which might be rendered in TT as:
[% vote = foo ? bar : '' %]
Since we don't have an explicit undef in TT (yet), I tend to use an
empty string; it seems to carry almost all the
Chris Laco wrote:
Off Topic. Making a note for myself and DBIC::Validation
100 can be validated because we have %colinfo {size = 100}
Patterns could be covered in validation_profiles at the source
level...but maybe this would be nice as well:
{
type = 'VARCHAR',
size = 100,
Brian Kirkbride wrote:
Jason Gottshall wrote:
Brian Kirkbride wrote:
I usually have an architecture like this:
Client - Controller - Model - ORM - Database
The ORM is usually just vanilla (as you suggested), the Database
enforces simple
data constraints (foreign keys, etc
Brian Kirkbride wrote:
I definitely have Models, but they are a higher-level abstraction than
the ORM
layer. If I understand your argument, you are advocating that data
constraints
imposed by your business logic be enforced by the the DB rather than
the ORM.
That's all fine and good, but
On Monday, February 26, 2007, Jay K wrote:
Well, finally, there is a new Catalyst::Plugin::Authentication module
available for general testing.
http://search.cpan.org/~jayk/Catalyst-Plugin-Authentication-0.
0_01/
JayK et al:
What's the status of this update? I'm starting a new project
