similar to: Lost default value of timestamp field.

I want to set default value to current time of database: class CreateUsers < ActiveRecord::Migration def self.up create_table :users do |t| # ... t.column :created_at, :timestamp, :null => false, :default => ''now'' end end #... end On postgresql, it is converted to: created_at timestamp NOT NULL DEFAULT ''2006-04-25

I''m having trouble getting the magical counter to work in a rails app with single table inheritance. following is the relevant code. thank you class declarations class Job < ActiveRecord::Base has_many :vents end class Vent < ActiveRecord::Base belongs_to :job, :counter_cache => true validates_numericality_of :width end class Rectangular < Vent

I''m trying out migrations for the first time, and I''m having a problem with my sqlite3 db. A trivial example of what I''m seeing: class InitDb < ActiveRecord::Migration def self.up create_table :mytable, :force => true do |t| t.column :lname, :string t.column :created_at, :string, :default =>

Hello, I''m trying to insert into my migrate but when I try on rails console this error shows: 1.9.3-p0 :001 > group = Group.new => #<Group id: nil, name: nil, description: nil, created_at: nil, updated_at: nil> 1.9.3-p0 :002 > group.name = "Group Name" => "Group Name" 1.9.3-p0 :003 > group.description = "Description" =>

I am at a lost for what is going on here-------I have a producttypes and categories table. prodtype_id is a foreign key in categories table that references producttypes table. Below is how I am tyying to display it and get the above error. Any suggestion </p> <b>Product type:</b><br/> <select name="Category[prodtype_id]"> <%

Hello It seems that datetime_select, is creating an instance of the Time class. Why would that be? I found this while building a site where people can create vigils (prayer vigils, peace vigils, etc). When I added a validation method that compared start_date to created_at, it generated the error: ArgumentError (comparison of Time with DateTime failed): I was able to put a breakpoint in the

Had this error when trying to add comments to another user''s photo. ActiveRecord::StatementInvalid in User photosController#show Mysql::Error: Unknown column ''comments.user_id'' in ''on clause'': SELECT photos.`id` AS t0_r0, photos.`user_id` AS t0_r1, photos.`title` AS t0_r2, photos.`body` AS t0_r3, photos.`created_at` AS t0.... I did create a user_id

Some how I''m getting NameError: uninitialized constant when accessing a child models that inherits form the parent model. However, if I access the parent model first, then the child model is resolved. What am I doing wrong? My steps are below... Thanks, Francis. > ./script/generate model Blah type:string class CreateBlahs < ActiveRecord::Migration def self.up create_table

Hi all. I keep having the following error when I invoke the rake db:migrate command for Rails 1.1 (Ruby 1.8.2 -- Windows 2000) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == Realtorex: migrating ======================================================= -- create() rake aborted! undefined method `create'' for

Dear Gurus on Rails! How do I change the behaviour of one method in ActiveRecord::ConnectionAdapters::SchemaStatements ? Full story: I''d like to mangle ActiveRecord::ConnectionAdapters::SchemaStatements so when it creates a new sql table, it also (optionally) creates my created_at, deleted, key_id, session_id etc columns that I use on basically all tables. It would not be DRY to repeat

Im trying to do the message board tutorial here but I have rain into a problem I get this error message SQLite3::SQLException: table posts already exists: CREATE TABLE posts ("id" INTE GER PRIMARY KEY AUTOINCREMENT NOT NULL, "body" text DEFAULT NULL, "created_at" d atetime NOT NULL, "name" varchar(100) DEFAULT NULL, "discussion_id" integer NOT

I am thinking that I have found a bug in Rails migrations. My app is using UUIDtools to generate guids for primary keys. To do this I pass :id=>false and then create my own id column as shown below. Next I leverage "execute" to create an index. It seems to work fine. The table in MySql is perfect. However the ID column and primary key on the ID column are not in the schema.rb file I

Hi In controller I have this query: @price_stat = Price.find_by_sql("select id, cost, tour_id, unix_timestamp(created_at) from prices") when I try to display result''s created_at column I don''t have any results: <% @price_stat.each do |p| %> <p><%= p.created_at %></p> <% end %> result is empty But if I try without unix_timestamp. ie:

I''m running a rails 2.3.5 / ruby 1.8.7 / postgresql 8.4.2 app and have just run into a curious problem. I have several tables that are initialized with data from csv files and I''ve noticed that, when I try to add new data to any of these tables via Table.new I get a PGError on duplicate key. For example: MIGRATION: class CreateNumbers < ActiveRecord::Migration def self.up

Hi, I am doing my first steps with RoR and I have the following problem: I execute my migration file with the following content on a MySQL-database via Rake: <code> class CreateUsers < ActiveRecord::Migration def self.up create_table :users do |t| t.integer :id t.string :username, :size => 100 t.string :password, :size => 100 t.string :email, :size

Hi everyone, For one of our projects we have a need to deploy and maintain a demo. As a result I''ve attempted to setup a set of rake tasks for the job. My goal is have one rake task called "deploy_demo" which purges the database, migrates to the current schema, and loads the db from a set of fixture files in a specified location. I''ve written two new tasks the perform

Railsers: I switched from MySQL to Sqlite3 for Test-Driven Development. It meant the difference between (Long term, I want to understand the db:migrate system well enough that I can run a long test, occassionally, that migrates everything to MySQL and retests it there. That will prevent nasty surprises at deployment time. But that''s not the current question!) Because I don''t

In an migration file there is one up and one down method. Below is from Agile Web Development with Rails: class CreateOrderHistories < ActiveRecord::Migration def self.up create_table :order_histories do |t| t.column :order_id, :integer, :null => false t.column :created_at, :timestamp t.column :notes, :text end end def self.down drop_table :order_histories end end Why is there a drop

Adds VmStateChangeEvent class and uses VmObserver to track/audit state changes for Vm objects. Callbacks in VmObserver also update the new total_uptime and total_uptime_timestamp attributes of Vm class, which allows easy calculation of time spent in running states for user resource use accounting. --- src/app/models/vm.rb | 34 +++++++++++ src/app/models/vm_observer.rb

I put this config in environment.rb # Use table_id instead of id for primary key. config.active_record.primary_key_prefix_type = :table_name_with_underscore I have this migration: class CreateEntities < ActiveRecord::Migration def self.up create_table :entities do |t| t.string :entity_name, :null => false, :limit => 40 t.string