5 ms·

Welcome to Rails circa 5 years ago! :)

• kayoone 13y ago
  Heck, even PHP frameworks have had migrations for ages!
• matthewrudy 13y ago
  Rails has had decent migrations for at least 7 years, probably longer. (I only started 7 years ago, and it was already pretty standard)
  • lectrick 13y ago
    Man, time flies...
• moe 13y ago
  Except no, Rails doesn't have this. Not even remotely close. Rails still makes you write your migrations by hand. It also forces you to distribute your critical constraints, validations and dependencies over a usually incomplete model class, and incremental migration files. In Rails/AR there is no place in the filesystem to find out about the currently declared schema. It's a fundamentally broken design.
  • bmckim 13y ago
    db/schema.rb
    • moe 13y ago
      schema.rb contains an _incomplete_ reflection on the current SQL schema. No references, no relationships. If you don't know the difference between AR and a declarative ORM you may want to refrain from dropping smarty oneliners.
      • collyw 13y ago
        He is a Ruby hipster. They are all about smart one liners.
      • lectrick 13y ago
        At absolutely no point in our dev team's existence did we find a huge need to have more than the model files and/or schema.rb as a schema reference. If you can't infer what you need to from there, then maybe web dev's not your bag, baby
        • moe 13y ago
          then maybe web dev's not your bag, baby Over the past 15yrs I've written web-apps in 7 different languages and a wide range of frameworks. From your comment I can infer that you know Ruby on Rails, and that's pretty much it. Maybe you should reconsider your tone?