similar to: Running migrations without shell access

The one thing I don''t like about migrations is the security, and I''d like to know if anyone is interested in working with me to improve it (or knows an existing way to accomplish the same thing). Here''s the scenario: - I always create specific database users that only have CRUD priveleges, and run my web apps with these users - I need to log in with a

Hi All Please excuse me if my questions sound silly. I have developed a rails app with an existing legacy schema and now with changes in customer requirements, I need to change the schema. The legacy (schema) database has > 250K. What I would like to know is 1. Is it possible to migrate the data along with migrating the schema if use Migrations? If it is possible can somebody point me to an

Hi, I was wondering if there is a way to skip the application of a named_scope to calls made in legacy migrations. I am working with some old migrations that include some data manipulation tasks, and my default scope is preventing those migrations from running. I''m trying to avoid editing those migration files with with_exclusive_scope. Thanks, -G -- Posted via

Hi, I''m trying to get my head around using migrations to define my initial schema. When using migrations, I want to: - Avoid creating a new migration for every small change. Limit it to one migration per checkin. - When creating a new (fresh) schema, I do not want to go through the overhead of all the migrations. These are the steps I came up with, to create the initial schema: 1.

I am developing against an existing database schema that I am enhancing with some custom tables. In the development and test database, I have basically generated "copies" of the legacy tables that already exist in production. So I have 12 migration files, some of which create dev/test versions of production tables and some of which create tables that will need to be moved to

I have a semi-grand plan for some changes to migrations. Mostly this is motivated by the upcoming 3.0 release and wanting to get migrations in engines working. 1. Don''t skip migrations with version numbers lower than "current". I only recently tripped over this, but apparently it''s been this way since 2.1 when we got timestamps masquerading as large/sparse

As many of you know, rake db:reset changed behavior just before Rails 2.0 got released. db:reset used to drop the database, re create it and migrate it up. The core team after integrating this feature, realized that it was not used as intended and instead db:create now uses the schema.rb file instead of the migrations. Check the many discussions we had about this topic, you will quickly notice

Hi! I'm deploying R behind a web-app on a linux-server and I don't want to grant the users shell access through the system() function for security reasons. Is there any safe way to deny a user access to the function? I tried a) alter the function in the R-Sources before compiling them. Doesn't seem to work because system() is apparently needed during the build. b) Redefine

I''m trying to get started with Rails, but I''m running into a few places where I''m having trouble understanding the expected workflow. I''m trying to work with migrations from the beginner; its a port of an existing application, but I''d like to let the db schema evolve as the application grows, so I''m starting from an empty (tableless) database.

Hi A newb question. Can I use migrations if all of the following requirements are imposed at the same time. 1. Copy data from an old schema to a new schema, the difference in the 2 schemas is about 25%, 3 new tables and 4 new columns. 2. Copy data from Oracle schema to DB2 schema, around 25% difference in 2 schemas as above. 3. Neither old nor the new schema tables have an

All, I''ve run into a situation where I want the owner of my DB tables to be different than the user that accesses them during application runtime. I believe that I can just set up another DB connection profile (with a name other than "production") in database.yml and then pass that as RAILS_ENV to db:migrate instead of "production". Anyone see any problems with

I love using ActiveRecord Migrations to build tables. Sometimes, I don''t want to use autogenerated PK''s - I want to set them automatically (why? I''m importing read only data from a large list of medications, and want to use the PK''s assigned by the medication research company...). Is there anyway to do this using Migrations? I know that I don''t

I''ve checked out a rails project that i''m working on from a repository, and created a new database for it. However whenever i try and run the migrations i get the following error: rake aborted! #<AppConfig:0xb7870f84> is not a class/module Whenever I try to fire up a webrick server, i get the following error: => Booting WEBrick...

I''m somewhat of a newbie - played with recent versions of rails a few mths ago, but have decided to start from scratch with 1.0. I want to build my new db as much as possible with migrations, so I watched DHH''s migrations movie from rubyonrails.org. A few things confuse me: 1. He generates the model ("post") before running rake db_schema_dump. Is that necessary or

I just started a tagging system for my site and I was getting funky errors when adding tags. I looked at the the data in the tables and realized that rails was only allowing me to save each tag once! Which meant that if i saved a tag for post 1, then i couldn''t associate that tag with any other post. Some head-scratching and cursing later, I remembered that join tables in HABTM

Guys, I''ve run across an interesting scenario with my migrations, and I hope you might share some insight. Let''s say I have 3 migrations and two Models (Person and Car): 001_initial_schema.rb 002_data_load.rb 003_add_car_association.rb The first creates the initial schema...the second loads default data using model objects of Person to do so, and the third creates a new

One thing I found annoying about Migrations, besides that you have a very limited ways to define your data, is that it will overwrite EVERYTHING in your schema file. So if you spend hours customizing your initial schema file, to get it work, exactly like you''ll need it, that work immediately becomes for nothing once you run a migration. Your entire schema will get rewritten, not appended

Hi. Is there some user friendly application (web based, maybe a webmail addon) that can help a user manage their sieve filtering? My mail users don't have any shell access to the mail host. Most users won't have a regular home directory either. Can I store this sieve information someplace else? Either directly in LDAP, or in some database, or a common directory for all user's

What is the best way to give a remote user the ability to use rsync via ssh without also giving them shell access? I want the rsync user to authenticate via ssh. I want to protect their rsync session with ssh. However, I do not want to give them access to a shell on the Linux server where rsyncd is running. Any recommendations would be appreciated. chongo (Landon Curt Noll) /\oo/\

Camping apps are supposed to be little independent apps, often contained in a single file, which create the database tables and manage them without hassle. These days it''s common to see in a Camping app: module Tepee::Models def self.schema(&block) @@schema = block if block_given? @@schema end end Tepee::Models.schema do create_table :tepee_pages,