similar to: schema_migrations table not created

Hi all! How can I change the name of the schema_migrations table? I have to do this because I can only use one database but want to have several rails projects. I hope this is possible at all. greets flo schaf -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on

Hi Puppet Users group, I have followed the guide to the puppet-dashboard DB "Preparing Schema" part, once I run " rake RAILS_ENV=production db:migrate --trace", it shows the following errors: (in /usr/share/puppet-dashboard) > rake aborted! > Mysql::Error: CREATE command denied to user ''dashboard''@''localhost'' for > table

I recently upgraded Cucumber gem from 0.1.16 to 0.3.11. I ran ruby script/generate cucumber. When I ran rake features I received an error telling me I had pending migrations and should run rake db:migrate. I ran rake db:migrate despite fact that my db is up to date. I was confused that the migrations ran from the beginning. However the migrations seem to have no effect on my database.

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

Hi, my company uses only 1 database for all the developments, so it is a big problem for using migrations in Rails because of the schema_info table. How can I solve this problem? Is there a way to change the schema_info table name? Thanks. Nicolas. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

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

I''ve created a table in a SQL Server database using a migration, successfully. I''ve tried to change the name of a column in the table and got the error message above when running ''rake db:migrate''. Previously I have developed using MySQL and Sqlite and migrations have worked successfully. This is an error I have not seen before. Has anybody seen this and worked

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/

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

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

We have a scenario where we have a core engine with module add-ons. What modules that will be used differ from deployment to deployment. Each of these modules might need different things in the db (both structure and data) and I want each module to be in charge of its own db structure. Each module is contained in its own source directory and what modules to use is determined in the build

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

Does anyone have MySQL replication set up for a Rails App that uses migrations? I''m having an issue where every time I run a migration Rails is trying to create the schema_info table. Mysql::Error: Table ''schema_info'' already exists: CREATE TABLE schema_info (version int(11)) This causes a problem on the slave databases where the replicated create table statement

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

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

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

I suspect this is because it is a 1.x application which was upgraded, but my migrations don''t "stick." If I Coder-iMac:patton colin$ rake db:migrate (in /Users/colin/Desktop/patton) == 20090217193953 AddLastYearToTarget: migrating ============================== == 20090217193953 AddLastYearToTarget: migrated (0.0001s) ===================== == 20090222192059 AddEditorToUser:

Hi, I am wondering whether it is possible to write and use migrations that do not change the schema_info.version. I would like to use the migration syntax to do certain tasks that don''t affect the schema like populating tables with sample data during development. Ingo -- Posted via http://www.ruby-forum.com/.

All, Database: SQL Server 2000 SQLServer adapter in ODBC mode I have a Capistrano deploy script which fails when I run against my production DB. Apparently, this is the because the user that is set up for production has "guest" privileges in my SQL Server database and when Capistrano runs, instead of looking at the dbo.schema_info table (which has the correct version # - yes I

(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