1.It depends on how much you want to optimize queries on the DB. 2.Not really, it is not supported ‘out of the box’ by AR. # As of Rails 4 enums are supported out of the box. 3.IMHO you can use strings without a big performance penalty (just remember to add field to an index). … Read more
drop the models project(put models into one of other parts, i’d suggest whatever you consider “more important”), put all projects into single repository(separate project folders) and make symlinks to models/libs/apis/whatever your code is highly coupled together and you often need to make changes to few projects at once(like updating models and updating APIs that use … Read more
The second method is the ideal way to handle this: your migration files are meant to represent how your database has changed over time. The older migration files will remain in your project (in case, hypothetically, you wanted to roll back to an older version), but Rails will not run them when you rake db:migrate … Read more
By convention in rails (and this is enforced by autoloader), file paths should match namespaces. So, if you have a Mailboxer::Message model, it should be in app/models/mailboxer/message.rb. Additionally, you probably have autoloader kicking in when trying to load a Message class (my guess is that it happens from within ActAsMessageable). It looks for a message.rb … Read more
Logic, OK it might sound a bit weak for this but it would be logical to say that “I have a supplier who has an account with me, I want to see the entire account history of this supplier”, so it makes sense for me to be able to access account history from supplier directly. … Read more