Also it looks like the SQL is searching for Twitter-1 vs. Twitter in the
condition:

>>> SQLite3::SQLException: no such table: extension_meta: SELECT
schema_version
>>> FROM extension_meta WHERE name = 'Twitter'

This stretches my knowledge of how Radiant/Rails uses the schema version- it
adds a "-1" to the extension name in the schema migration table? But I can
see how it's not working, since it won't find that record.

Anna

On Wed, Nov 18, 2009 at 10:31 AM, john muhl <johnm...@gmail.com> wrote:

> maybe you ran the initial migration on the production db and then the
> uninstall migration on the development db.
>
> On Wed, Nov 18, 2009 at 12:04 PM,  <subsor...@gmail.com> wrote:
> > Thanks for the reply, I did:
> >
> > rake production db:migrate:extensions
> >
> > ==  AddTwitterNotificationFields: migrating
> ===================================
> > -- add_column(:pages, :notify_twitter_of_children, :boolean,
> {:default=>false})
> >   -> 0.0358s
> > -- add_column(:pages, :twitter_id, :string)
> >   -> 0.0024s
> > ==  AddTwitterNotificationFields: migrated (0.0397s)
> ==========================
> >
> > and the columns were added to my database.
> >
> > In the schema_migrations I have Twitter-1 as the last entry...
> >
> >
> >
> > On 18 Nov 2009, at 17:19, banane wrote:
> >
> >> Did you ever migrate the Twitter extension? "rake
> >> radiant:extensions:twitter:migrate" - look in the schema version table,
> and
> >> if there's no reference, you didn't, so your undo doesn't know what to
> undo,
> >> basically.
> >>
> >> On Wed, Nov 18, 2009 at 7:58 AM, <subsor...@gmail.com> wrote:
> >>
> >>> Hello all,
> >>>
> >>> I just decided to try out the the twitter extension, but then decided
> to
> >>> remove it as it couldn't pull in multiple feeds.
> >>>
> >>> When I tried to roll back the migrations with this command:
> >>>
> >>> rake radiant:extensions:twitter:migrate VERSION=0
> >>>
> >>> I got this error:
> >>>
> >>> SQLite3::SQLException: no such table: extension_meta: SELECT
> schema_version
> >>> FROM extension_meta WHERE name = 'Twitter'
> >>>
> >>>
> >>> Dropping columns in SQLite is a bit of a headache, so is there another
> >>> command to use, or how can I fix this error in order to roll back
> easily?
> >>>
> >>> Thanks in advance,
> >>>
> >>> Dominic
> >>> _______________________________________________
> >>> Radiant mailing list
> >>> Post:   Radiant@radiantcms.org
> >>> Search: http://radiantcms.org/mailing-list/search/
> >>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
> >>>
> >> _______________________________________________
> >> Radiant mailing list
> >> Post:   Radiant@radiantcms.org
> >> Search: http://radiantcms.org/mailing-list/search/
> >> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
> >
> > _______________________________________________
> > Radiant mailing list
> > Post:   Radiant@radiantcms.org
> > Search: http://radiantcms.org/mailing-list/search/
> > Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
> >
> _______________________________________________
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
_______________________________________________
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to