example apps say to use :id => false, this is bad form

[evanweaver]

In some cases it also leads to bugs for RDBMS systems that don't take :auto_increment => true nicely.

Is in blog.rb, and possibly others. Has been tripping up the Scots.

[why]

YES.

[evanweaver]

The manual column additions:

t.column :id, :integer,:null => false

need to be excised too. (blog.rb and campsh.rb).

[mikemondragon]

Replying to evanweaver:

The manual column additions: t.column :id, :integer,:null => false need to be excised too. (blog.rb and campsh.rb).

This is the hack I have in camping/session.rb line 62 of gem installed Camping 1.5

create_table is defaults to :id => true and the explicit :id column does not need to be explicitly declared.

This makes a Camping app I'm writing happy with the mysql-2.7 and sqlite3-ruby-1.2.1 adapters and AR 1.15.3. I'm on Debian Lenny x86.

    def self.create_schema
        unless table_exists?
            ActiveRecord::Schema.define do
                create_table :sessions, :force => true do |t|
                    t.column :hashid,      :string,  :limit => 32
                    t.column :created_at,  :datetime
                    t.column :ivars,       :text
                end
            end
            reset_column_information
        end
    end

[zimbatm]

Does [205] solve the problem ?

[zimbatm]

Checked on #rubyonrails, werdnativ says that the id is automatically created.

To understand the issue : the automatically incremented :id column definition, highly depends on the RDBMS. For example, MySQL has the non-standard auto_increment attribute. I think, Oracle needs a stored procedure, ... The best way is to let ActiveRecord handle the case. Apparently, it takes the right decision for you :)