Re: Suggestion: default values for models

Gabriel Sobrinho
Thu, 18 Oct 2012 12:50:30 -0000

That is a problem for me either.

I can''t use before_save callback because I need to show the default
value
on forms.

So, I have a date field and the default value is today, but when user open
the form, today must be on that field.


I''m setting this kind of default value on controller like that:

def new
  @payment = Payment.new
  @payment.date = Date.current
end

But this become a mess since I have "dynamic" default values in almost
every model of my application.

On Wednesday, October 17, 2012 4:41:55 PM UTC-3, Zamith
wrote:
>
> Isn''t this just the same as having a before_save callback where
you define
> these default values?
>
> Also, what do you mean with "We can use db''s default values
but they are
> evaluated during migrations"?
> On Oct 17, 2012, at 8:28 PM, Alexander Kurakin wrote:
>
> ROR doesn''t realize functionality of setting default values for
models. We
> can use db''s default values but they are evaluated during
migrations. We
> can''t set default value i.e. Time.now. But there are completed
gems that
> realize this. I.e. default_value_for (
> https://github.com/FooBarWidget/default_value_for). Why not to merge it
> in rails? Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rubyonrails-core/-/u1PNgYmkABUJ.
> To post to this group, send email to
rubyonra...@googlegroups.com<javascript:>
> .
> To unsubscribe from this group, send email to
> rubyonrails-co...@googlegroups.com <javascript:>.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
>
>
> Cumprimentos,
> Luís Ferreira
>
>
>
>

--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Core" group.
To view this discussion on the web visit