search for: biot023

Hallo -- I''ve just installed the latest stable version of rails, and am following the rails recipies book''s first recipie -- using in_place_editor_field. My problem is that the code throws no error, but the resulting fields are not editable -- the values just come up as text, rather than clickable-then-editable fields. Can anyone help shed any light on why this might be the

Hallo -- is there a way anyone know of that I can add a :confirm clause to a form submit? Something like: <%= submit_tag ''commit'', :confirm=>"are you certain?" %> Does anyone know how to achieve this? Cheers, doug. -- Posted via http://www.ruby-forum.com/.

Hi -- all the docs I can seem to find are related to running puppet with passenger, but not installing it. Does anyone know of any recipes I can use to actually install passenger with my server''s Ruby and Apache installs? Thanks, Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

I like Shoulda. Sometimes I like plain old Test::Unit. Cucumber gives me a different thought process. I''d just like to hear some thoughts on why RSpec? What does it buy me that I can''t get with Shoulda? I just can''t seem to think in RSpec. Where is there a good example of RSpec tests that will help me grasp the right path? Thanks! -- Amos King

Hi -- I''m trying call apply in standalone mode on a configuration I''ve written. The way I call the command is like this: $ puppet apply manifests/site.pp -v --modulepath modules The directory structure is simple: . manifests/site.pp manifests/nodes.pp modules/ ... site.pp just includes nodes.pp, and nodes.pp looks like this: https://gist.github.com/3181007 When I

Hallo -- I have the most bizzare problem. I have a test called PropertyTest that runs absolutely fine. Even if I totally clear the test database before running it, it happily scoots off, loads all necessary fixtures, runs & passes all tests. My problem arises when I run rake test:units. Then, all other tests pass fine, but this one starts failing as if the fixture data simply

Hi -- if I have a class that declares ''validates_associated'' on a number of other classes, is it supposed to be relatively easy to replace a collection of them? Not to overwrite them in the DB, but simply to assign them to their retrieval method, so that they can be included as part of the owning class'' validation. I mean like: children_with_potential_errors =

Hi, I have a class (say Parent) that has many of two other classes, say FirstChild and SecondChild. These could look like this: class Parent < ActiveRecord::Base has_many :first_children, :dependent => true has_many :first_children, :dependent => true validates_associated :first_children validates_associated :second_children end class FirstChild < ActiveRecord::Base

Hallo -- can anyone offer me any pointers as to I should handle many-to-many relationships in Rails tests? Cheers, doug. -- Posted via http://www.ruby-forum.com/.

Hi -- I have a need to run the following SQL in a test: "DELETE FROM agents_bookings" Does anyone know of a way that I can just execute this? It is to clear a many-to-many relationship in the teardown function of a test. Cheers, doug. -- Posted via http://www.ruby-forum.com/.

Hallo, I have a table like this: create table properties( id bigint unsigned not null auto_increment, property_variable_stack_id bigint unsigned not null, primary key(id), foreign key (property_variable_stack_id) references property_variable_stacks (id)) type=InnoDB; Here you can see a reference to a table property_variable_stacks. >From outside the Property class I can set up a Property with

Hallo -- could anyone tell me how I use Migrations (which my existing development schema is implemented with) to create the production database for deployment? The target DB is a SQL Server database -- I don''t know if that''s an issue -- I seem to remember reading that SQL Server is supported now. Oh, yeah -- SQL Server was *not* my choice! But what I seem totally unable to

Hi -- I''ve got a very strange error. I have an action called ''commit_input'' on a controller called ''SiteVisitController''. This definately exists, and is called from the functional test for it, and passes fine. My problem is with the form that is supposed to call this action. The form tag is: <%=