You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 21, 2024. It is now read-only.
This tripped me up because I ran into the problem in 0.6.1 where the column names weren't quoted. Once I forked your github repo though, I realized that you're on v0.7.0 and that the problem had since been fixed. Can you release this to rubyforge?
The text was updated successfully, but these errors were encountered:
Also, any reason that you don't have github building this either? It's a pain to have to instruct my team to download this library and build it themselves. If you include a .gemspec file in your repo, and mark this project as a rubygem in github, github will build it and host it for you.
Then in my gem manifest file for any project, I can reference the build on github (if for whatever reason you can't release to rubyforge). I'm happy to help if you're unfamiliar with these practices...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This tripped me up because I ran into the problem in 0.6.1 where the column names weren't quoted. Once I forked your github repo though, I realized that you're on v0.7.0 and that the problem had since been fixed. Can you release this to rubyforge?
The text was updated successfully, but these errors were encountered: