similar to: Postgres plpgsql is created by default in new version, but schema dump tries to create it

(in C:/projects/books/TheatreTickets) ** Invoke db:test:clone_structure (first_time) ** Invoke db:structure:dump (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:structure:dump ** Invoke db:test:purge (first_time) ** Invoke environment ** Execute db:test:purge ** Execute db:test:clone_structure psql:db/development_structure.sql:15: ERROR: language

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

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

Hi, In my environment.rb, I have set: config.active_record.schema_format = :ruby Whenever I do a rake db:migrate, both db/development_structure.sql and db/schema.rb get generated. This shouldn''t happen should it? I thought I should only get db/schema.rb? Thanks, Jordan

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 haven''t seen anyone mention this yet. The tail end of the migration process is a call to schema.dump. Our primary keys are uuids and these choke schema.dump on both oracle and postgres. The latter fails silently (skips three tables) while the former complains about the RAW(16) in each of the three tables. Anyone had a similar experience? -- Posted via http://www.ruby-forum.com/.

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

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, I am trying to figure out the status of Hieraki project. It seems that the software in use in manuals.rubyonrails.com is old and the new(er) version is quite different. Is this correct? I am somehow confused because in seems that the project wiki/track is under "spam attack" ( http:// www.hieraki.org/trac/timeline ). Also it seems that there is only mysql schema for the

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

If you used MySQL FULLTEXT indexes and just upgraded to Rails 1.1, watch out for this one. Rails 1.1 now defaults to Ruby as your schema format. So instead of development-structure.sql, Rake will use schema.rb. That''s portable and good stuff overall but there is a slight compatibility issue. Ruby schema doesn''t know how to do FULLTEXT index syntax for MySQL. To work around it,

Hi, I have the following migration (abbreviated): class Initial < ActiveRecord::Migration def self.up create_table :messages, :options => ''ENGINE=MyISAM'', :force => true do |t| t.column :id, :integer, :null => false t.column :external_id, :string, :null => false t.column :recipients_count, :integer, :default => 0

So after successfully getting the test SQLite db to run from memory, I tried running some tests but found that somewhere in the schema translation from Postgres (my devel database) and SQLite Rails fails to properly set the ''id'' column, which breaks all kinds of things. Take as an example my ''users'' table. In Postgres the schema is (generated with pgAdmin III):

Hi, is this the best forum to answer this question? Is there any better source for information or another mailinglist to address this question to? Cheers, Mariano ---------- Forwarded message ---------- From: Mariano Kamp <mariano.kamp@gmail.com> Date: Jan 8, 2006 6:24 PM Subject: Migration doesn''t seem to preserve create_table options in schema To: rails@lists.rubyonrails.org

Played around with rails on mysql a little bit. Now I''m looking at rails on postgres, and postgres has schemas. Wondering if it''s appropriate to create *schemas* for my three db evironments (development, test, production) rather than separate dbs? b

Rails/Postgres Gurus, Question: Is it possible to use Postgres schemas within a Rails app to separate tables and data between two different apps? Problem Set: I am thinking of combining two apps. I want to share some data (certain tables) between them, but I want the migrations and other activities to be separated. I don''t want any table changes in one app to impact the other.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm using Postgres as dict backend now and then I get this error, when someone changed ACLs, actually for some reason some users, who get permission from other users, get this error quite often: dict: Error: sql dict: commit failed: ERROR: duplicate key value violates unique constraint "user_shares_pkey" (query: INSERT INTO

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, 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