e does
> not get set, which is reasonable behavior the moment you are dealing with
> time. I am unsure whether there is another create method which uses
> database or even the schema column spec.
>
> Regards
>
> Robert
>
> On Sat, Dec 10, 2016 at 5:48 PM, LNATION .
Hi,
I understand that there is a complicated solution. I am looking for
the simplest way.
Doc says:
For forms where you pass in an 'item' (usually a database row object),
the values in that object will be used preferentially; if an accessor
exists in the 'item' object, then the defaults won't b
process()?
Regards
--
M.
On 2016.12.10 15:36:10 +0100, Martin Řehák wrote:
> Hi Gerda,
>
> sorry for late reply. Didn't have time to look into this.
>
> Now I have:
>
> my $init_row = $c->model('DB::Lesson')->new_result({});
> $valid
Hi Gerda,
sorry for late reply. Didn't have time to look into this.
Now I have:
my $init_row = $c->model('DB::Lesson')->new_result({});
$validated = $self->formDetail->process(item => $init_row);
And I still don't see the database defaults in the rendered form. Any clue
where to