search for: createpages

Hello, I have the problem posted at this address : https://github.com/svenfuchs/globalize3/issues/172. I created a new project with a new model and I integrated globalize3. I created a migration like this : class CreatePages < ActiveRecord::Migration def up create_table :pages do |t| t.timestamps end Page.create_translation_table! title: :string, body: :body end def down drop_table :pages Page.drop_translation_table! end end W...

...ables, it runs once and it''s done. But what happens if the next version of Tepee adds a field? Well, you write some code to sniff out that field in the database, right? == V and Its Float == Here''s how I could rewrite Tepee to use the V class: module Tepee::Models class CreatePages < V 1.0 def self.up create_table :tepee_pages, :force => true do |t| t.column :title, :string, :limit => 255 t.column :body, :text end Tepee::Models::Page.create_versioned_table end def self.down drop_table :tepee_pages...

Hello, This is a follow-up to Adam’s original RFC (RFC: First-class Matrix type, [1] <http://lists.llvm.org/pipermail/llvm-dev/2018-October/126871.html>) <https://confluence.sd.apple.com/pages/createpage.action?spaceKey=DPT&title=1&linkCreation=true&fromPageId=1360610956> and his follow-up ([RFC] Matrix support (take 2, [2