similar to: rake db:test:prepare

hey guys, I''m having a problem here, I have a pc in my house that I use as a db server (postgresql). I have the pr-postgresql gem running and it works very well But when I try to "rake spec" I get these 2 errors C:/ruby/bin/rake: No such file or directory - dropdb -U "coleira" coleira_test C:/ruby/bin/rake: No such file or directory - createdb -E unicode -U

Hi, I get errors doing this: 1) createdb myapp_test 2) rake db:test:clone_structure 3) rake test:units rake aborted! PGError: ERROR: relation "matches" already exists I''m using the :sql schema format because there are some problems with postgres and the :ruby schema format config.active_record.schema_format = :sql It seems rake test:units is trying to create the tables

I have spent sometime this afternoon learning how to unit test rails applications and integrate the Cerberus CI tool. One key area confuses me however, and I would appreciate other peoples views of how best to overcome the issue. My understanding is that the ''test'' and ''test:units'' have the db:test:prepare pre-requisite which copies the schema from dev to the

http://dev.rubyonrails.com/changeset/856 looks to me like it''s not going to work, since there''s no way of specifying a password to pg_dump/dropdb/createdb. If you set PGPASSWORD in your environment it might work, but that''s not documented anywhere and isn''t done automatically in the Rakefile. See http://thread.gmane.org/gmane.comp.lang.ruby.rails/3693 for

Hi all. I am using PostgreSQL in my current project and I have couple of questions on this topic. Previously I have used 3 databases for project. i.e. megaproject_development, megaproject_test and megaproject_development. But I don''t like this variant because of ''rake dump_db_structure'' writes a lot of PostgreSQL specific data for structure file (operators, functions,

TDD, SVN and migrations seem to be a natural combination for model development: create a test, add the column with a migration, write the code, and check it all in when you''re done. The trouble is that this ends up creating one migration per field. I guess it''s not horrible in and of itself, but it does have a code smell to it. Has anyone come up with a different way of doing

Hello All, If I run my unit tests individually using Ruby, they all work correctly. However, if I try to run them using "rake test_units", I get a bunch of error messages. The error messages appear to be caused by rake not loading any of the fixtures into the test database. I am using PostgreSQL on Windows. Does anyone have any suggestions? Many thanks, Bruce. -- Posted via

I''m writing some code that accesses some lagacy database on PostgreSQL. Since the old database had some really ughly and weird naming conventions (like CamelCase). To work around this I created a second schema (named rails) in the same database and gave the tables and fields some rails-friendly names. The database user that Rails uses has its search_path set to the rails schema. That way

Hi I am using postgres and have two migration files like 001_create_categories.rb as class CreateCategories < ActiveRecord::Migration def self.up create_table :categories do |t| t.column :name, :string, :limit=>80 end end def self.down drop_table :categories end end and 002_populate_categories.rb class PopulateCategories < ActiveRecord::Migration

Hello, When I try to run "rake clone_structure_to_test" on my project, I get the following errors: $ rake clone_structure_to_test (in /home/www/cedscreening) psql:db/development_structure.sql:8: ERROR: permission denied to set session authorization psql:db/development_structure.sql:16: ERROR: permission denied for schema public psql:db/development_structure.sql:34: NOTICE: CREATE

anyone able to explain logic behind "rake spec" startup? i.e. the below steps & why things occur when they do Macintosh-2:myequity greg$ rake spec --trace (in /Users/greg/source/myequity) ** Invoke spec (first_time) ** Invoke db:test:prepare (first_time) ** Invoke db:abort_if_pending_migrations (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute

Folks, I don''t like that I have to grant CREATEDB rights to the test user to get testing working smoothly with Postgres. What is the philosophical reason that Rails wants to drop and recreate databases during the testing? It would seem to me that "pg_dump -c" (the "clean" dump option, similar to mysqldump''s --add-drop-tables ) would suffice when

I have a test environment running rails 1.2.3. I am just starting to introduce testing into this project. When I run a rake db:prepare. I see this message "Mysql::Error: #42000BLOB/TEXT column ''short_description'' used in key specification without a key length: CREATE INDEX ''short_description'' on cached_cars (''short_description'') The

Signed-off-by: Joey Boggs <jboggs at redhat.com> --- installer/modules/ovirt/manifests/freeipa.pp | 8 ++++---- installer/modules/ovirt/manifests/postgres.pp | 12 ++++++------ 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/installer/modules/ovirt/manifests/freeipa.pp b/installer/modules/ovirt/manifests/freeipa.pp index e5de852..f91cd43 100644 ---

Hey all, I''m trying to create a task that prepare the environment to start programming. To do so, I created a task like this *task :setup_env => [''db:reset'', ''db:migrate'', ''db:test:prepare'']* and observed that after execute * rake setup_env*, it never execute db:test:prepare properly. In order to get the schema cloned to test db,

How to empty DB in heroku<http://stackoverflow.com/questions/4820549/how-to-empty-db-in-heroku> I have a Postgres database on Heroku. It is one of the free beta ones. Locally, when testing, I often run rake db:drop && rake db:create && rake db:migrate as a way to reset the database. However, when I try to run this on Heroku, I get the error:\[code\]Couldn''t drop

I''m trying to use new_equipment_path, which creates the appropriate link. But, when trying to evaluate "equipment/new" I get the error below. I''ve included my routes (rake route). Equipment is one of those words that pluralizes to "equipment", so the singular is right (from what I know from this forum. Any help would be appreciated. Error: equipment_url

I am a newbie to RoR and I''m having trouble getting testing up and running. I tried Googling my problem and haven''t found an answer that has worked. When I run rake db:test:prepare, I get the following error (I''m working with the RailsSpace book): Macintosh:rails_space myusername$ rake db:test:prepare (in /Users/myusername/Documents/rails_projects/rails_space) rake

As far as I can tell, if I''m using MySQL and I set the character set and collation on my databases when I create them (e.g. CREATE DATABASE project_development CHARACTER SET utf8 COLLATION utf8_general_ci), when I run db:test:prepare it''ll lose that information because db:test:purge drops and recreates my database without bothering to check what my character set and collation

Hi In the model I have User attr_accessor :validate_email_id validates_presence_of :email ,:if => :validate_email_id Could anybody please tell me how can I define a Factory for the above? Thanks in advance Sijo -- Posted via http://www.ruby-forum.com/.