similar to: unit test question

Sans rails my normal approach to handling this would be to enforce it in the database and when a database operation failed I''d try to validate the model to produce an error message. It''s always served me pretty well. Rails expects you to validate before commiting but of course this does nothing to guarantee referential integrity. It''s perfectly possible for one

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

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

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

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/.

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

Anyone have any tips for handling postgres constraints when using fixtures to load the database, other than to sort out the proper insertion orders or leaving the constraints out? I''d prefer not to do the former since I''d rather use my app to generate my fixture data (using a dump_fixtures task) and I''d prefer not to do the latter because leaving out constraints till the

I''ve upgraded to Rails 1.1.2, and I''m trying to push this change through to our build server (Linux/Oracle) and we are getting some errors in the unit tests using Oracle. Looking at the data in the tests reveals a precision problem. Looking at the tables tells the whole story. My development database contains this table: SQL> describe dls_grids; Name

I recently started using migrations to create the schema of a Rails project I am working on. The database I am using for this project is MySQL. The initial migration creates the table and also includes a number of execute statements (to do some things like setting primary keys, autoincrement on some columns and other messy voodoo). Running "rake migrate" creates the database with no

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

Hi Folks, There is much discussion where I work at present regarding migrations, and the ''correct'' usage or not of them. TL;DR Should migrations be used just to modify schema, and other ''deploy'' tasks done other ways? If yes, how to ensure no repeat runs of such tasks (seeds, jobs etc) Background Once you''re live there are often additional things

All, It looks like rake db:schema:dump does not dump primary keys. I have some legacy table that don''t follow the convention ie pk = id and none of the primary keys for these tables are getting dumped... Seems strange as this should be readily available from the db. I am using MySQL. Is anybody else seeing that ? Incidentally how does one specify a primary key using

After upgrading to 1.1, I can''t run any unit tests. Apparently when I run rake test_units, it uses a migration to set up the database. Unfortunately when it runs the migration, it''s adding not null constraints to every field, even though I haven''t got that set up. I''m using the ruby-postgres (0.7.1.2005.12.21) adapter with PostgreSQL 8.1.0. I''m

Hi, when I execute dispatch.cgi at the command line, I get the following error message: [cg@cg rails]$ ./public/dispatch.cgi ./public/dispatch.cgi:3:in `require'': ./public/../config/environment.rb:8: syntax error, unexpected ''<'' (SyntaxError) <%= ''# '' if freeze %>RAILS_GEM_VERSION = ''<%= Rails::VERSION::STRING %>''

Hi guys, I need your help. Here is my database.yml: development: adapter: postgresql database: db username: username password: mypassword # Connect on a TCP socket. Omitted by default since the client uses a # domain socket that doesn''t need configuration. Windows does not have # domain sockets, so uncomment these lines. host: 192.168.22.1 (this is a remote ip in

On 2/5/06, Joe Van Dyk <joevandyk@gmail.com> wrote: > On 2/4/06, Jonathan Weiss <jw@innerewut.de> wrote: > > Joe Van Dyk wrote: > > > Hi, > > > > > > I''d like to set up CIA. So I added the plugin to my app, went to my > > > subversion server, added the post commit, added a build directory. > > > > > > I checked

I just got a new PC at work. My project files were copied from my old drive. Just to be sure, though, I have erased them and pulled them back down from source control. My development database server is MySQL My test database server is sqlite3 I am having a confusing issue: tests are failing and errors are happening that weren''t happening before. Furthermore, they aren''t

I am getting a rake aborted error and I suspect that I am missing a package on my system since the app works for a friend on this computer. Here is the terminal output of the error: anita@anitas-computer:~/sandbox/shovell$ rake db:migrate (in /home/anita/sandbox/shovell) rake aborted! Could not find table ''stories'' (See full trace by running task with --trace)

Hi, I''d like to use migrations to build my initial database. Is there a gem or plugin that will generate the migration code for initial db if I point it at a live database or sql file? If yes, then can you automatically generate the incremental migrations as well? Thanks, Jason

Hello All, Yesterday i put RoR with Locomotive. I am very happy :p. So I follow this tuto (http://developer.apple.com/tools/rubyonrails.html). I used Sqlite. my database.yml # MySQL (default setup). Versions 4.1 and 5.0 are recommended. # # Get the fast C bindings: # gem install mysql # (on OS X: gem install mysql -- --include=/usr/local/lib) # And be sure to use new-style password