20 Jul
2012
20 Jul
'12
14:57
Hi, I now face one design issue we have in SLMS. We mark schema.rb as non-config and handle failed write during db:migration. I think that it is not good approach and schema.rb should contain correct state of database. How do you handle such situation? mark schema.rb as config or symlink somewhere in /var/lib? Ignore it? Josef -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org