search for: jeff_lamarche

After creating a table in a create table migration, I''m then attempting to populate a couple of rows of data in the table using the create method. The first row gets inserted into the database, but any further calls generate a select against the database, but no insert. Am I doing something wrong, or is it inappropriate to create more than a single row of data in a table using

I''m currently using ruby-postgres (the compiled interface to PostgreSQL), and I''m seeing a huge performance hit with larger :binary fields in ActiveRecord subclasses owing, it appears, to the use of the bytea field type and the fact that using that datatype necessitates an in-memory "unescape" conversion. The best I can tell from looking at the Postgres Active

Hi, I would like some suggestions. I''m wondering if it''s better to upload a file directly into a database or to put the file into the server and keep the path in the database? Thanks, Eric -- Posted via http://www.ruby-forum.com/.

Please excuse a newbie question, but I couldn''t find anything by searching the archives. What I want to know is how to have multiple references to the same class/table within a class. For example, let''s say I have a table called People: create table people ( id serial8 primary key ,name); which just holds a list of the people in the database. Then I have another

I''ve been playing around with RoR for a bit now, and am starting to really get my head around it. Now that I''m starting to feel comfortable with Ruby and Rails I''m trying to learn a little more about deployment, and am hitting a problem. It''s probably something dumb, but the Agile Rails (2ed) book''s chapter on deployment doesn''t answer my

I''m noticing a different behavior between development and production environments when I use caches_action along with send_data. I have a method: def image @thePic = Picture.find(params[:id]) send_data(@thePic.image.data, :filename => @thePic.image.filename, :type => @thePic.image.content_type, :disposition => "attachment") end Which works fine; it

I need to store rather large data in the database using blobs. I''ve been working with Rails and have designed a proof-of-concept setup that works pretty well, except there''s a considerable performance hit with very large files due to the fact that ActiveRecord loads the entire blob into memory before the data can get passed to send_data. I know at least one person is going