rake db:seed only works when in its own rake

Asked Jun 20 '17 at 19:48

Active Jun 20 '17 at 19:48

Viewed 111 times

Here's two commands while using attr_encrypted:

# Seed fails to populate encrypted fields
rake db:drop db:create db:migrate db:seed

# Seed succeeds
rake db:drop db:create db:migrate
rake db:seed

When I say that seed 'fails', I mean that the encrypted fields are all blank. When it succeeds, the encrypted fields are populated.

An example from the seeds file:

Company.create_with(  
  key: "12345"  
).find_or_create_by(  
  name: "Acme Inc."  
)

Why is this happening, and how can I make sure seeds works every time?

asked Jun 20 '17 at 19:48

sscirrus

My guess is it needs to reload context / code / db structure. – Sergio Tulentsev Jun 20 '17 at 20:08
@SergioTulentsev Is there a way to tell the seed file to reload these things every time? – sscirrus Jun 20 '17 at 20:13
it's not the seed file that needs reloading, it's rake. – Sergio Tulentsev Jun 20 '17 at 20:14
Hence my question... it won't be obvious in future if this stuff doesn't work, so is there a way to reload rake (or reload context/code/db structure) after my migrations or before my seed? – sscirrus Jun 20 '17 at 20:22
It's just a stab in the dark, though. And yes, you reload everything by running rake another time. :) – Sergio Tulentsev Jun 20 '17 at 20:27

0 Answers0