Update: not sure why this hasn't been fixed in the pivotal branch, but I've published my branch to gemcutter (http://gemcutter.org/gems/bborn- desert), and you can use that, just add this to your .gems file (if you're on heroku):
bborn-desert (or use gem 'bborn-desert', :lib => 'desert' require 'desert' If you're just working with pgsql locally) Thanks! Bruno On Oct 12, 2:18 pm, SS <[email protected]> wrote: > Okay! Looks like I had the error and solved it. Yay!!! > For all of you that experience the same issue please follow those > instructions: > > 1. Please check in your RUBY_GEMS\desert-0.5.2\lib\desert > \plugin_migrations if you have more than one versions. I had 1.2 and > 2.1 and the migration operation was confused which one to grab. I > think it was grabbing the first one. > > 2. I modified line 10 in schema_statements.rb under RUBY_GEMS > \desert-0.5.2\lib\desert\plugin_migrations\2.1\extensions > > from: > plugins_and_versions = select_all("SELECTplugin_name,versionfrom # > {Desert::PluginMigrations::Migrator.schema_info_table_name}") > > to: > plugins_and_versions = select_all("SELECTplugin_name,versionfrom # > {Desert::PluginMigrations::Migrator.schema_migrations_table_name}") > > I think this is a line that never got changed by Desert development > team. An issue like that was reported a few months ago and it should > have been fixed in the latestversion0.5.2 but looks like it got > missed. > > http://groups.google.ca/group/pivotallabsopensource/browse_thread/thr... > > I hope this post helps you guys and you don't get frustrated like > me! ;) > > Cheers! > > -Siyan > > On Oct 12, 1:53 pm, SS <[email protected]> wrote: > > > It looks like there is some type of inconsistency between Desert and > > Postgresql:http://groups.google.ca/group/pivotallabsopensource/browse_thread/thr... > > > I believe that if I can resolve the following error, it will fix the > > original error message that I reported above. > > > PGError: ERROR: relation "plugin_schema_info" does not exist > > LINE 1:SELECTplugin_name,versionfrom plugin_schema_info > > ^:SELECTplugin_name,versionfrom plugin_schema_info > > > It all worked well when I used CommunityEngine with MySQL.... > > > Any insights guys how to fixing that dependency? It's driving me > > crazy :( > > > On Oct 11, 11:44 pm, SS <[email protected]> wrote: > > > > I'm trying to move CE from MySQL to PostgreSQL database. I'm having > > > trouble running 'rake db:migrate' after creating the databases. Has > > > anyone gotten this error message: > > > > == CommunityEngineToVersion70: migrating > > > ===================================== > > > rake aborted! > > > An error has occurred, this and all later migrations canceled: > > > > PGError: ERROR: current transaction is aborted, commands ignored > > > until end of transaction block:SELECTversionFROM > > >plugin_schema_migrationsWHEREplugin_name= 'community_engine' > > > > I'll appreciate your help! > > > > Siyan > > -- You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/communityengine?hl=.
