I think having an option to enable built-in callback logging is a great
idea.
There have been many times when I wanted to temporarily log AR callbacks in
order to debug something. It would be nice to have it built-in to the
framework so we don't have to worry about the callback implementation
chan
Yes, in 4.2.5 it is. But after rake db:migrate I not seen it. This behavior
is strangely. This confused me, and so I created this topic.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving em
No problem at all. I'm really not sure if the deprecation is there so if it
is not please let us know so we can fix this.
On Tue, Jul 5, 2016 at 4:11 PM Andrey Molchanov wrote:
> Thank you, I will be more attentive
>
> вторник, 5 июля 2016 г., 22:08:31 UTC+3 пользователь Rafael Mendonça
> França
Thank you, I will be more attentive
вторник, 5 июля 2016 г., 22:08:31 UTC+3 пользователь Rafael Mendonça França
написал:
>
> Yes. And I think in Rails 4.2 it show a deprecation warning to tell people
> that it is going to default to null: false in Rails 5
>
>
> On Tue, Jul 5, 2016 at 4:07 PM A
Yes. And I think in Rails 4.2 it show a deprecation warning to tell people
that it is going to default to null: false in Rails 5
On Tue, Jul 5, 2016 at 4:07 PM Andrey Molchanov wrote:
> My bad. Yes, it is. But in 4.2.7 it is`n. You specify not add it in 4s
> versions?
>
> вторник, 5 июля 2016
My bad. Yes, it is. But in 4.2.7 it is`n. You specify not add it in 4s
versions?
вторник, 5 июля 2016 г., 22:00:37 UTC+3 пользователь Rafael Mendonça França
написал:
>
> I think this is already the default in Rails 5. Isn't?
>
> On Tue, Jul 5, 2016 at 3:52 PM Andrey Molchanov > wrote:
>
>> Hi t
I think this is already the default in Rails 5. Isn't?
On Tue, Jul 5, 2016 at 3:52 PM Andrey Molchanov wrote:
> Hi there!
> If we create migrate with
>
> t.timestamps
>
> it will add lines
>
> t.datetime "created_at"
>
> t.datetime "updated_at"
>
> In schema.rb file.
> What are you think about i
Hi there!
If we create migrate with
t.timestamps
it will add lines
t.datetime "created_at"
t.datetime "updated_at"
In schema.rb file.
What are you think about if *by default* in this case null option will be
false without explicitly specifying?
--
You received this message because you are s
+1
I had this idea too. It's annoying when looking at diff when something changes
and it's not obvious.
If someone wants to take a stab at it, please feel free.
-Prem
> On Jul 5, 2016, at 8:08 AM, Xavier Noria wrote:
>
> Positive over here. People may occasionally have a look at db/schema.
Positive over here. People may occasionally have a look at db/schema.rb,
but it's main use case is to automate stuff.
Personally, I wouldn't even make it configurable in this case, we are not
talking about generating a non-readable dump. Some people would even write
it like that if it was their co
Yes please :+1:
Dealing with that cruft mismatch in schema.rb is a headache --- would defiantly
speed up developer productivity if we figured out the reasons why different
developers' systems produce slightly different files (this being one of them)
and killed those nuances so my schema.rb did
11 matches
Mail list logo
