similar to: Rails 1.1: not-null constraint violations

Hi, I''ve got a table with an inserted_at column. When I insert a record it automatically injects the current date/time, all is well. Then when I insert a second record, it uses the exact same timestamp that is used in the first record. This behavior only seems to occur in production mode. When I restart the server, the problem goes away but then immidetatly occurs again on the

There is a table: execute (<<-SQL) CREATE TABLE "tasks" ( "id" serial primary key, "number" serial, "version" integer DEFAULT 0 NOT NULL, "latest_version" boolean DEFAULT ''t'' NOT NULL, "hidden" boolean DEFAULT ''f'' NOT NULL, "type" character varying (1) NOT

I''m using Restful Authentication, and the code to create a user is pretty straight forward - there is a before_save action and a before_create action: before_save :encrypt_password before_create :make_activation_code But for some reason when I try to create a user programmatically in the controller like this: User.new(:email =>

Hi, has anyone successfully used the acts_as_threaded plugin with postgresql? I''m using rails 1.0 and ruby 1.8.4 on linux. Following the screencast on http://www.railtie.net/articles/2006/02/05/rails-acts_as_threaded-plugin , I got to where we''re ready to create our first post, having made the changes to controllers/posts_controller.rb, views/posts/_form.rhtml,

I know this has got to be a really dumb question, but here goes anyway. I''ve got a model with an associated table. One of the columns in the table is ''date_created'', which I want to be set to the date/time each row was added to the table. Seems to me that setting this in the initialize method for the model would be the right thing to do,... class MyThing <

Hi, I am having a small problem concernig how to access local variables in before_create. I am not sure how to really form this question but here goes: I am wondering why this works def before_create self.last_logged_in = Time.now self.created = Time.now end but this doesn''t def before_create @last_logged_in = Time.now @created = Time.now end The latter fails

Hi, for some reason, all timestamp fields with or without time zone in my Postgres tables seem to be casted to nil. From console: >> me = User.find(''PS12345'') => #<User:0x2379788 @attributes={"mtime"=>"01.03.2006 13:26:32.737166", "valid"=>"8", "valid_from"=>"01.03.1999 14:09:21 CET",

Filed a ticket for bogus Ruby produced via: rake db_schema_dump http://dev.rubyonrails.org/ticket/3232 I''d appreciate it if someone could verify against PostgreSQL 8.0.x -- -- Tom Mornini

I wanted to fix some things up in the trunk, so I set up the databases and ran the unit tests. A bunch fail for postgres, and even more error out. I know of two postgresql adapters: postgres-pr and ruby-postgres. Strangely, they each fail different tests. So if I want to fix things up, which one should I be using? For that matter, which adapter should I be using for production? Finding out

To Whom It May Concern: I have an ActiveRecord-based application (non-Rails). Life was grand until I upgraded ActiveRecord yesterday, after which point I was getting TONNES of these errors from my app and in PostgreSQL''s logs: FATAL: terminating connection due to administrator command According to Google searching, this happens when an external process sends PostgreSQL SIGINT or

Hi everybody, Small problem. I get this error: undefined method `all_categories'' for BlogCategory:Class Code of BlogCategory class is: class BlogCategory < ActiveRecord::Base has_and_belongs_to_many :blog_posts validates_presence_of :name validates_uniqueness_of :name # Return all categories ordered by name def all_categories find :all, :order =>

Not sure if this is possible currently. I have a section of code like this: ActiveRecord::Base.transaction do cow.save! duck.save! dog.save! end (Names changed to protect the innocent.) I''d like to specify that the saves run in a transaction. I can do ActiveRecord::Base.should_receive(:transaction).and_yield But is there any way to specify that the code is

Hi all, I am exploring using RoR for a new project but have run into a problem with ActiveRecord and SQL Server''s timestamp datatype. We have a NOT NULL timestamp column in a table and ActiveRecord keeps trying to update it, which promptly causes it to blow up. I have tried making the value NULL for insert and update in the model, but SQL Server doesn''t like that

I have a new @offer that needs to generate a document if saved. But that''s all or nothing: transaction do @offer.save! generate_document end # handle exceptions if needed If save! fails everything is fine, but if generate_document raises an exception @offer is left as a model with timestamps, id, which is not a new_record? anymore (though the database was

Hi, Every once in while I have to run SQL by hand, in my models mostly. But I''m wondering if there is a better way of doing it than I do. And, I have a question concerning types of the fields in the result the query produces. First, about the types. In a certain model, to get and return the value of a boolean function, I have to do: result =

Hello all, Is there a method for updating all the attributes from a hash without saving to the database? (the counterpart of update_attributes but without saving). What I want to do is: person = Person.find(params[:id]) person.update_without_saving(params[:person]) #update the in-memory object. # Process person object ....... person.save I know that when you are creating a new object, you can

In console, I am trying to create a User but the :account_id does not come in. Console just gives me back :account_id => nil. Obviously I''m trying to set it though. Silly console... But, I can set the account_id column in my controller like so: @user = User.new(params[:user]) @user.account_id = account.id @user.save Here''s what I give to the controller: User.create :name

Hello to all! First I want to appologize if this topic has been already discussed but the search does not work :) I have RoR installed on a shared server. I also have a RoR application installed in a subdomain. The structure is as follows: www //this is my home WWW folder +--- www //maps to www.mydomain.com | +--- webapp //maps to webapp.mydomain.com. Here is my RoR application |

I''m running a rails 2.3.5 / ruby 1.8.7 / postgresql 8.4.2 app and have just run into a curious problem. I have several tables that are initialized with data from csv files and I''ve noticed that, when I try to add new data to any of these tables via Table.new I get a PGError on duplicate key. For example: MIGRATION: class CreateNumbers < ActiveRecord::Migration def self.up

I am not sure that this is entirely a rails question as I am trying to run the command in postgres and I am getting the same error... controller code... @client_slot_count = ClientSlotsDaily.find(:all, :conditions => ["created_at > ? AND created_at < ? AND facility_id = ? AND client_id IS NOT NULL", starting_date, ending_date, @facility.id],