rake db:seed error

[gosuri]

PGError: ERROR: relation "schema_migrations" does not exist
LINE 4: WHERE a.attrelid = '"schema_migrations"'::regcl...
^
: SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull
FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
WHERE a.attrelid = '"schema_migrations"'::regclass
AND a.attnum > 0 AND NOT a.attisdropped
ORDER BY a.attnum

Tasks: TOP => db:seed => db:abort_if_pending_migrations

[dcleven]

When you run db:seed rake uses ActiveRecord to check for pending_migrations. Which queries the public.schema_migrations table, which doesn't exist in public, it is in global.

[dcleven]

Is this a viable solution?

In config/application.rb
config.active_record.table_name_prefix = 'global'

[gosuri]

HI filo,

Apologies. I accidentally deleted your question on github. It should be okay to add to existing applications.

Greg Osuri
Twitter (http://twitter.com/GregOsuri) • Blog (http://gregosuri.com?tracking=sig)
Mobile: +1 (415) 683 1097 • Skype: greg.osuri

On Wednesday, October 12, 2011 at 10:54 AM, Doug Cleven wrote:

Is this a viable solution?

In config/application.rb
config.active_record.table_name_prefix = 'global'

Reply to this email directly or view it on GitHub:
#4 (comment)

[filo47]

Greg,

Thank you so much for getting back to me. I recently
converted my rails app to mutlitenancy following the code in a recent
railscast
(http://railscasts.com/episodes/389-multitenancy-with-postgresql). I
wanted to try your solution to see how they compare.

My question is,
HOW DO YOU RE-CREATE TABLES IN NEW SCHEMAS FOR MODELS THAT PREVIOUSLY
EXIST? Running a shared migration does nothing because my migrations
have already been run. Running the tenant migration only adds a tenant
schema not the needed tables?

Thank you for the help,

Phil Hemmers