similar to: rails + svn automation script

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

Hi. What is the best way to pre-populate your database with records while developing, not testing? For example, I want to: 1) > [run this command to populate db] 2) > ruby script/server 3) now I can surf to localhost:3000 and my app will already have relevant data I''m hoping to use yaml to suck it in. Is there a way to use the Fixture class to handle this even though this is

When I set the rails_env to production in nginx.conf I get: Error message: db_name must be a string or symbol -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to

Hello, I'm trying to set up a mailbox for a bunch of domains. To do so I'm running some docker containers (I know I can use multidomain set up and I'm doing so, but I need to have some domains on different containers for specific reasons). In order to keep it all clean, I want to use different PostgreSQL databases for each container, and I'm running the container with an

This is my first rails app with a legacy database and I''m having a terrible time getting the models set up correctly. I have an order table that has a primary field named order_number. I have a name table with a primary of item_number. These two tables are liked by the item_number and the order_number, but not as you might think. If the order_number is 2500, then each entry in

Hi all, I''ve got some tables with fixed amounts of data in them (a "states" table, for example). For tables like this I can easily put *all* of the data in the fixture. For general futzing purposes, and for those times I want to reload a database from scratch outside of testing (for whatever reason), what''s the best approach? I thought perhaps ActiveRecord::Base had

I have a few projects with large directories (say, user-uploaded files) that make using Capistrano a bit awkward. However, I suspect that I may have reached the "write a custom task" level. (I suppose I''m just thinking out loud, here...) It seems as though I''d want this directories symlinked in /shared... Maybe there''s a way to extend the

Hi (I''m resubmitting this because First question: This is the rails dev list, correct? I''d like to submit a patch and am following the steps on this page: http://dev.rubyonrails.org/ Here''s what I did (using mysql 5.0.15-nt): created 2 databases: activerecord_unittest activerecord_unittest2 created 1 user: rails (giving all priveleges to both databases) ran

In my daily development, I migrate back and forth between versions, and often do: rake load_fixtures... ... in order to populate my development database with fun data. Now, with any HABTM relationship, there are failures, as there is no way to say "which" fixtures to load first. Within an actual functional or unit test case, you could simply load them in the proper order, but

I am getting an error that I can''t figure out. I have a class called Test with 3 fields, id, x, and y. When I do Test.new(''x''=>1, ''y''=>2).save, I get an error saying that id (my ''not null primary key'') can''t be null. But isn''t active record supposed to deal with setting that for me? Here''s the code

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone know what''s going on with ActiveRecord Edge and 1.2RC1 unit tests. I get 13 failures from the "async_exec" method call. ie: test_callback_rollback_in_save(ConcurrentTransactionTest): ActiveRecord::StatementInvalid: NoMethodError: undefined method `async_exec'' for #<PGconn:0xb75a8754>: SET

Recently I''ve wanted to be able to take the data I''ve painstakingly defined in my fixture files and slurp it up into my development database so I can play with my website (locally, in development mode) with the same data I use in my tests. In a similar vein, I want to take the table definitions in the development_structure.sql file and use it to re-define my development

I left ":memory:" in database.yml for testing and the most simple tests in the Agile book do not work (see trace below for test_truth). Since that''s what comes with the distributed database.yml I suppose it''s me doing something wrong. Did someone get SQLite ":memory:" working? How does it grab the schema? -- fxn % rake test_units (in

Here is my file to parse and load extensions. No wise cracks about my code.... DB.php is the Pear DB module. (pear.php.net) <?php include('DB.php'); $db_host = ''; $db_name = ''; $db_login = ''; $db_pass = ''; $db_table = 'extensions_table'; define(DBINFO,"mysql://$db_login:$db_pass@$db_host/$db_name"); $db =

The new gem version dependency system from Rails 1.1.1 needed a few tweaks to work properly and to stop throwing meaningless warnings. This tiny release makes up for that. To install: * gem install rails * rake rails:update:configs (to get the latest config/boot.rb) This release also signals our new commitment to do more tiny releases from the stable branch, which only gets bug fixes. So it will

I want to have Rails 1.1 + Rails 1.0 on the same PC and be able to load my script with a different version each time. Is it possible? -- Posted via http://www.ruby-forum.com/.

Is there an easy way to use fixtures outside of a rails app? I''m using activerecord for a project and would love to use fixtures as well, but I haven''t found any info on doing this. I''m hoping it''s something quick and simple someone can explain to me so I don''t have to dig through the rails source :) -- Posted via http://www.ruby-forum.com/.

Hi all, I just released RSpec 0.7.3. It''s got a few bug fixes and the rails plugin *should* run against both Rails 1.1.6 and 1.2.0-RC1. If you run into problems, please report bugs and feature requests in the tracker at rubyforge: http://rubyforge.org/tracker/?group_id=797 Cheers, David

It was said at one time that Rails 1.1 might be released in February. Is that still likely? Thanks, Don Mc -- Posted via http://www.ruby-forum.com/.

Now that Rails is doing regular updates to 1.1.x branch, is it possible to track the this release using svn:externals inside my app? Currently I have: rails http://dev.rubyonrails.org/svn/rails/tags/rel_1-1-1/ in my vendor directory. Can I change this to something like a wildcard ''rel_1-1-x'', ensuring that I always have the latest of the stable 1.1 branch? Cheers! Tom