schema.rb not being generated correctly after migration about activeuuid HOT 4 OPEN

@patrick-gleeson I've had this issue in both Rails 4.2.5 and 4.2.6. It does makes sense that this may be a compatibility issue with newer versions of ActiveRecord since this gem seems to have fallen out of maintenance.

My work-around was to use structure.sql instead of schema.rb by adding the following line to config/application.rb:

config.active_record.schema_format = :sql

See http://edgeguides.rubyonrails.org/active_record_migrations.html#schema-dumping-and-you

from activeuuid.

@cameronbourgeois what version of Rails are you using?

We just upgraded from Rails 4.0 to Rails 4.2, and now every time we run a migration, in the schema file every table that had a uuid 'id' column loses its id column entirely, even if the migration itself is for something completely unrelated.

If our problem is the same thing as yours, that suggests the problem isn't with your migration syntax, it's with how this gem interacts with ActiveRecord in Rails 4.2.

@jashmenn, this repo hasn't had any commits in 10 months - is it still being maintained by anyone and is there a reasonably chance that anyone will be able to look into this?

from activeuuid.

Ah nice one! Yep, that's working for us too as a workaround.

from activeuuid.

@patrick-gleeson - I've added you as a contributor! Feel free to make commits directly!

from activeuuid.