Ticket #4 (closed 1: wontfix)

Opened 2 years ago

Last modified 1 year ago

Zack

Reported by: albert@delamednoll.se Assigned to: somebody
Priority: 1 Milestone: 1
Component: 1 Keywords: Zack
Cc: Zack

Description

Hi!

This project seems very promising! I just downloaded and tried to set it all up and ran into some small problems.

I skipped your setup.rb though, and went straight into migrating, and i found some small issues. Firstly, the initial data cannot be input with the current trunk code, this is resolved by moving the init to last migration.

Secondly, the first migration doesnt work for me, i had to remove the limit on the integer types in the user table.

Thirdly, postgres does not seem to like doing change_column from integers to booleans, i had to do this:

def self.up

remove_column "users", "admin" add_column "users", "admin", :boolean, :default => false, :null => false remove_column "users", "developer" add_column "users", "developer", :boolean, :default => false, :null => false

end

This ofcourse drops the information stored, so another method might be better.

Attachments

rake.output (61.5 kB) - added by albert@delamednoll.se on 05/02/06 09:14:53.
this is my test output, running the trunk

Change History

05/02/06 09:14:53 changed by albert@delamednoll.se

  • attachment rake.output added.

this is my test output, running the trunk

05/02/06 11:06:46 changed by jlong

  • status changed from new to closed.
  • resolution set to wontfix.

The model objects have changed as columns have been added and removed from the schema. This prevents you from doing rake db:migrate on a fresh db. Instead, you should run the db/setup setup script first before running migrations. As I understand it migrations only designed for development and should not be used in production. There will be scripts provided to upgrade the database when changes are made in the future.

Feel free to e-mail me, preferably on the mailing list if you think this should be different. I am very open to discussing it.

I am setting this ticket to resolved for now. Please file a separate ticket for the Postgres issue.

06/02/06 16:25:56 changed by Main

  • type deleted.

spam

06/06/06 21:04:08 changed by Home

  • type set to defect.

spam

06/13/06 01:52:05 changed by Link

spam

07/03/06 02:37:41 changed by anonymous

  • priority changed from major to critical.
  • type changed from defect to task.
  • version set to 1.0.
  • component changed from component1 to component2.
  • milestone set to 0.6-Lapidary.

spam

07/03/06 02:37:48 changed by anonymous

  • priority changed from critical to major.
  • type changed from task to defect.
  • version deleted.
  • component changed from component2 to component1.
  • milestone deleted.

spam

08/04/06 21:46:03 changed by Zack

  • cc set to Zack.
  • component changed from component1 to 1.
  • summary changed from Problems running rake migrate to Zack.
  • priority changed from major to 1.
  • version set to 1.
  • milestone set to 1.
  • keywords set to Zack.
  • type changed from defect to 1.

spam

06/17/07 01:32:08 changed by fdas

spam