Displaying 20 results from an estimated 20000 matches similar to: "Use Migrations in modules in separate source trees?"
2006 May 24
10
Ferret slow after a while
I''m building a new index from scratch based on a number of documents
stored in a database loaded using my Rails env (using Ruby Ferret 0.9x
(installed today with Gem) on Windows). At first everything goes nice
but after a number of documents it starts to go slower and slower until
it grinds to a halt (at least feels like it).
Am I doing something wrong? Is there some way to work
2006 Jan 19
3
problems with migrations in sql server
Is anyone using migrations with a SQL Server database who might be able to
lend me a hand? I''ve used migrations with MySql in the past and haven''t
run into any issues so forgive When I run rake migrate nothing is actually
getting updated in my database. I created a migration using
./script/generate migration AddFooTable and updated the migration to look as
follows:
class
2006 Mar 08
3
migrations schema_info table, Rails Recipes Bug?
I have the rails recipes book and i was going through the migrations
recipe. Everything seemed to work except for the last part in trying to do
a rake migrate with a migration file version 1 and the schema_info version
set to 0. Without the force attribute, the rake migration fails, as
expected.
So the recipe says to run this:
ruby script/runner
2005 Dec 14
3
Plugin w/ Migrations and/or Fixtures?
I''m working on a plugin which needs to add both schema and data to the app
database, and I''m trying to figure out the best way to do it. I''d like to use a
db migration to modify the schema and load the data from a YAML fixture, but
Rails doesn''t seem to support migrations for plugins. To do so, the schema_info
table would need to change to include a
2007 Mar 08
3
Problem loading data from database
Hello, I get this error trying to load some data from DB. I''m using
Rails 1.2.2 on Fedora Core 6 and Sybase adapter.
This worked fine when application run under Rails 1.1.6 but now I''m
migrating to 1.2.2 and have some problems.
At browser I got:
SQL Command for table_structure for tplib_bckps failed
Message: schema_info not found. Specify owner.objectname or use
sp_help to
2005 Dec 23
1
Better way to import initial migration?
On a rails app that I''m developing I converted a regular old .sql file
into a rails migration. Since I generated the migration in my
development environment, it created the schema_info table for me.
However, when I updated my production environment and tried running
rake migrate it complained that schema_info doesn''t exist. Is there a
rake task for getting around this yet, or
2006 Jul 10
2
Problem with migrations, postgresql, AWDwR
Hi all,
Rails 1.1.4
Rake 0.7.1
PostgreSQL 8.1.4
Windows XP Pro
I checked for errata on pragmaticprogrammer.com, but didn''t see any
explicit mention of this issue.
I''m going over the depot example in AWDwR, 2nd ed, and I can''t get the
migration to work on p. 82. Specifically, the AddTestData example (with
reduced description text to save my fingers some typing):
2006 Apr 17
1
migration issue
of course, now that I am relying upon migrations, I''m at a loss to
explain why it isn''t working.
I have a system which has production and development and I have a
development system at home where I created all the new code and
migrations.
I committed my changes via svn and used ''svn update'' to update the live
system.
I started by running the migration on the
2006 Jan 26
2
Render and publish to static files?
What would be the best way to publish a number of pages to static html
pages? Just loop through them and create URL:s and fetch them with http
or is there a better way?
tia
/Marcus
2006 Jun 18
1
Problem using "rake db:migrate"
Hi all,
I am facing a problem while using rails "migrate" feature for creating
tables in a database.
Following are the details.
I have 2 applications say "app1" & "app2". I want both of them to use same
database say "testdb".
For "app1", I create 3 models which in turn create 3 migration files with
prefix, 001_, 002_ & 003_. Now I
2007 Jul 09
1
Issue with version field in schema_info
(I know ''version'' is the only field, but in case this changed one day my
question will still apply) ;)
I had to drop all my tables to re-run my migrations from version 1. When
I executed ''rake db:migrate'' everything ran successfully. Which puts my
database ''state'' at migration 007_xxx.
Now when I add a migration (008_xxx) and re-run
2006 Aug 08
6
rake migrate the first time - uses more than schema_info?
All,
I have two migration files, file 1 and file 2.
For reasons that I don''t want to go into unless I must, I want to only
run file 2 on my production database (file 1 contains a bunch of table
creation stuff for already existing tables).
I figured if I created a schema_info table and set the version in it to
1, then I could just run rake db:migrate RAILS_ENV=production and just
2006 Apr 05
16
Migration won''t rollback to specific version?
Hi all,
I''m confused about how migrations work. I''ve been using them for a
couple of weeks but haven''t had any serious rollback issues yet. Just
now I added a field to a table with a migration and ran "rake migrate",
which added the field as expected.
This was in the file db/migrate/007_mymigration.rb, making it version 7.
Later I changed my mind and
2008 Apr 23
2
Table Unknown - SCHEMA_INFO
Hi all,
Sorry for another newbie question!
I''ve got a legacy firebird database which I wish to use, and thanks to
help from this group I''ve used Dr Nic''s Magic Models to get RoR
talking to the database.
However, I wish to create a new table ("reports") in this database,
and so generated the scaffold such that the file "db/migrate/
2006 Feb 13
5
now that I have migrations working (I think I do anyway)
Do I now define database changes directly in
db/migration/0001_add_a_new_table
file ?
Obviously the point is not to make the changes directly in postgresql db
anymore right?
Thanks
Craig
2006 Jul 06
1
migrations work from script/console, but not command line
Having a weird issue where I can migration to version 1, but then go
no further, and cannot go back to 0 -- but only from the command line.
If I open up script/console I can do migrations just fine - down to 0
or up to 2, via ActiveRecord::Migrator. So I know the migrations must
be valid, and I can verify that tables are created or destroyed in the
database.
Does anyone have any idea why this
2006 Aug 01
10
Migration DB Question
Just going through ''agile web development with rails'' 2nd ed.
I accidentally created an empty migration source file with the wrong
name,
ruby script/generate migration add_test_date
and then straight after that created the one I wanted to use
ruby script/generate migration add_test_data
and populated the second one - when I ran
rake db:migrate
a few times it did not seem
2006 Apr 01
1
UTF-8 in migrations: problem with broken chars in db
I need to put some data into the database using migrations. The data
needs to be in UTF-8 format (since the database and the rest of the
Rails application is UTF-8). It doesn''t work.
I have set up the UTF-8 support in environment.rb (which works perfectly
in the rest of the application). I have also tested to save the
migration file as a UTF-8 file (variable char length), as a
2007 Sep 26
0
Fwd: error with schema_info when doing multiple migrations
Posting to merb list in case it is a merb problem. (?!??)
The error still happens with sequel 0.2.1.
---------- Forwarded message ----------
From: Kevin Williams <kevwil at gmail.com>
Date: Sep 23, 2007 10:26 AM
Subject: error with schema_info when doing multiple migrations
To: sequel-talk at googlegroups.com
I tried to post an issue to the project site but it kept giving me 500
server
2006 Aug 05
5
rake migrate error: nil.first
My migrations were working fine until today. I dropped and re-created the
database.But, when I go to apply my migrations, rake migrate aborts with
this error.
You have a nil object when you didn''t expect it!
You might have expected an instance of Array.
The error occured while evaluating nil.first
Any idea what might be wrong? The migrations look right. It''s talking to
the