The problem is that we try to run "which" on windows which does not exist. This works with Ruby 1. On Ruby 1. I'll add a fix for that. Sorry, something went wrong. Looks like we need better handling of windows paths. Could you try manually inserting backslashes instead of forward slashes in the original line? We have no core developers on windows, so the support is poor. I am planning to install a windows VM for testing. All help is greatly appreciated.
Running the Ruboto test suite on windows would be great. OK, thanks. That is not the same file, but "dx. Could you post the contents of dx. It will take me a while to get proper windows support working. Ruboto 0. Hi carr0lls! Could you try with Ruboto 0. Make sure you run ruboto setup in your project. All ActiveRecord versions 4. Are you certain you did bundle install? When you do gem list sinatra-activerecord activerecord , does it list both gems? I not use example, because something not use.
If use example, I can't check what different. Only use very simple test code for check. Ok, put a minimal non-working example Sinatra app into a Gist, because I can't reproduce it.
I no use They just try to change this order. Ok, then I'll close this, and other people will report if the problem comes up. This is a list of paths where you require from. Think of it as shell's PATH variable, where shell searches for executables that you want to run. So, on it's own, Ruby just requires the latest version of ActiveRecord, which may not be the version you want.
That's because require in Ruby is a bit smarter, it knows where are your gems. So, if it isn't able to require something from the load path, it will search in gem directories.
In this specific case I'm using load instead of require because I have to require a. That's why you need Bundler, to add ActiveRecord to the load path so that load can find it. Btw, thanks for reporting this, I realized that in the readme I don't prepend the rake commands with bundle exec. Hi there, I'm using bundle exec rake:db migrate which executes fine in my console. However, it hasn't updated my schema. I've tried running rake db:migrate a few times and it still hasn't updated the schema.
Is there a step I'm missing? I would appreciate any feedback at all RE this problem! When you run rake db:schema:dump , does it update your schema appropriately?
Thanks for your reply. However, when I check the file properties, it shows that it was modified after I ran rake db:schema:dump.
That's really weird. It caught my eye on your migration output that both CreatePackages and CreateOrders migrations took 0 seconds to execute. Is it possible that you left them empty? Notice that the version timestamp in schema. Since heroku doesn't allow you to copy files to their hosts outside of version control, you have to check it in to work on heroku.
That said, I'm trying to figure out ways to make this more intuitive for folks working both on heroku and elsewhere, so I'll be sure to add this to the documentation and such. Ran into the same problem Skip to content.
Star New issue. Jump to bottom. Copy link. Any thoughts? I'll comment here anyway : Since that fill will be different for every different instance of citizenry, I didn't want to bundle the settings. Oh okay. I appreciate the explanation.
BTW, I was in Portland this past weekend Sign up for free to join this conversation on GitHub.
0コメント