similar to: test:clone_structure problems with Postgres

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,

am in a bit of a quandry... I have asked postgresql-users list and haven''t gotten anything to work with... > > How do I change the owner of a schema? > > > > ALTER SCHEMA "public" OWNER to "some_user"; #? > > http://www.postgresql.org/docs/current/interactive/sql-alterschema.html > > The docs explain this very situation. HTML

As of some recent version of Postgres, plpgsql is created for new databases by default, but the sql schema export (config.active_record.schema_format = :sql) expots a create command in development_structure.sql, resulting in an error. CREATE PROCEDURAL LANGUAGE plpgsql; I could not find the version this changed in, however it is noted here:

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

I''m using a "CHARSET=utf8" option in my migrations, but this isn''t dumped to schema.rb - a file that test:db:clone uses to create the test database. The end result is some of my specs fail because they''re expecting the db table to be using utf8. to get round this, I switched to using db:test:clone_structure which DOES preserve the charset option, but when the

Hello, I have tried to install the salted hash login generator by following the quick start guide at: http://wiki.rubyonrails.com/rails/pages/SaltedLoginGeneratorQuickstart. Everything seems to work fine until I try to run the unit tests by doing ''rake test_units'', then I get the following error message: <error-message> [brasse@keso login-test]$ rake test_units (in

Hi, Using rake with Postgresql gives the following error: psql:db/development_structure.sql:13: ERROR: must be owner of schema public I''m using the latest version of rails and postgresql 8.0 on ruby 1.8.3 (2005-06-23) [i486-linux]. The above error occurs when rake clones my dev database to test - it first came to my attention when I ran "rake" for my first unit tests. It

Hello, I am having some trouble running the unit tests for the salted has login generator. I am a bit new to both ruby and rails so I am having a little trouble deciphering the error message I get when running ''rake test_units''. Up till the point where I try to run the unit tests I have followed the quick start guide for the salted hash login generator

When I do ''rake clone_schema_to_test'' I get this: (in /var/www/rails1) rake aborted! ./db/schema.rb:34: syntax error, unexpected tCONSTANT, expecting kDO or ''{'' or ''('' t.column "datetime", :datetime, :default => Sun Mar 05 03:19:39 MST 2006, :null => false ^

I''m sure people have encountered this before, but I''ve been unsuccessful at finding anything about it. Basically, I got a rails app that uses postgres and tsearch2 for some full text indexing and I''d like to be performing unit tests. Now, there''s the whole deal of how to get the test database to load all the tsearch2 information properly. I tried to come up

In development and production, I''ve got postgresql constraints that prevent deleting a CaseManager if there is a Client that belongs to that CaseManager. In unit tests...and obviously in my testing db, those restrictions don''t get added. Is it wrong to test for deleting dependent records in unit tests? Craig --~--~---------~--~----~------------~-------~--~----~ You received

I''m using add_foreign_key_constraint and remove_foreign_key_constraint from Bubbleshare''s Active Records Extension plugin now to manage the foreign key relationships I describe in my other recent posting. The constraints get added within migrations, but I''m running into two problems (Rails 0.14.3, PostgreSQL db): 1. Dumping the schema doesn''t dump the

Hello I have a problem that has exhausted my ingenuity and would like pointers to a solution, or at least where to debug. - I am using R and postgresql. - I have databases on two different servers. - I have a few users, who use different client machines - whose R installations are identical (rsync'd) >From one client machine I can access databases on both servers, using both psql and by

Hello everyone, I''m trying to migrate a working app from Postgres to MySQL, and I''m trying to use a migration to get it done rather than alter all my database table creation scripts to MySQL syntax. I''ve done loads of work with Postgres, but am a real newbie with MySQL... I did a ''rake db_schema_dump'' from my Postgres app, and got a nice looking

People, I''m looking at the migrate example on p 74 of the rails2.pdf It''s a simple example of using a migration to add a column to the products table. Here is a copy of the migration file named 002_add_price.rb after I generated and then edited it: class AddPrice < ActiveRecord::Migration def self.up add_column :products, :price, :decimal, :precision => 8, :scale

I installed at least one gem since I thought I actually once was able to run ''rake appdoc'' command since there is an api for my models and the ez_where plugin that I installed earlier. I wanted to see the api for pdf-writer which is the gem that I installed most recently. (no, I haven''t given up the issue of ''looping'' that Kevin and some others replied

Hi, When I run rake, everything works fine but when I run rake test:units I get an error apparently while it''s trying to create db tables saying the table already exists. I ran rake with trace to see the differences. It appears that rake test:units does db:schema:load twice, maybe that is the problem? Anyone know why this might be? Output of trace below Rake ** Invoke default

Hi, I noticed that db/development_structure.sql file somehow appeared in my project... Why is it generated? what is it good for? I see it has my db schema. but I already have my db schema in another file I created. thanks! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

hi list - i recently attempted to run rake for a first pass at some tests and ran into a mysterious failure. rake indicated that it had aborted running the tests but provided little information on exactly why this occurred. the only bit of information it did offer was that i could use --trace for a full trace. of course i did that hoping it would provide more detail, but it didn''t help a

Hi! When I run test:units, rails complains about the tables already being present. They had to be present so I could run individual unit tests. So why doesn''t rails just drop the tables if they exist? Any ideas?? Jeroen debug oupt below: >rake test:units --trace (in ...) ** Invoke test:units (first_time) ** Invoke db:test:prepare (first_time) ** Invoke environment (first_time)