Update to use "deprecated" version 3.0.0 #8

Open
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

Update to use "deprecated" version 3.0.0 to get rid of "already initialized constant Deprecate" warning.

rubygems defines its own Deprecate module in rubygems/deprecate.rb. This causes a warning when deprecate 2.0.1 is required because it aliases the Deprecated module to Deprecate. Version 3.0.0 no longer does this aliasing and gets rid of the warning. Updating to 3.0.0 requires some changes in how methods are deprecated, and how set_action is called.

@jinschoi jinschoi Update to use "deprecated" version 3.0.0 to get rid of "already initi…
…alized constant Deprecate" warning.

rubygems defines its own Deprecate module in
rubygems/deprecate.rb. This causes a warning when deprecate 2.0.1 is
required because it aliases the Deprecated module to
Deprecate. Version 3.0.0 no longer does this aliasing and gets rid of
the warning. Updating to 3.0.0 requires some changes in how methods
are deprecated, and how set_action is called.
fe3bb90

+1 Can we get any committer attention?

The deprecation warning is a problem. We've got a pull request. Is this gem maintained? Do we need to fork it?

@jinschoi I emailed project owner to see if there was any chance of this pull request being accepted, and he just responded "No" with no explanation.

What are you currently doing? Using a custom forked version? Just dealing with the deprecation warning? Something else?

The deprecation warning is making some things more complicated for me in an environment where something is running in a cronjob watched by something that thinks output on stderr represents a potential problem someone should be notified about (and indeed I usually try to keep my cron scripts from outputting anything to stderr unless there is a problem someone should be aware of, but impossible here due to deprecation warning)

I'm just using a forked version. Last I checked, most ruby dbi work had moved to rdb and there seems to be little interest in maintaining ruby-dbi. I cannot move to rdb because of the poor existing backend support for non-mysql databases.

Thanks @jinschoi. Interesting. I am using ruby-dbi in order to get
JDBC support under jruby. For the Sybase JDBC driver. I wonder if
there's a better option for this?

Otherwise, if you have your forked version in a public git repo, want
to share the connect details, and maybe i'll use that?

On Wed, Feb 22, 2012 at 10:58 AM, jinschoi
reply@reply.github.com
wrote:

I'm just using a forked version. Last I checked, most ruby dbi work had moved to rdb and there seems to be little interest in maintaining ruby-dbi. I cannot move to rdb because of the poor existing backend support for non-mysql databases.


Reply to this email directly or view it on GitHub:
#8 (comment)

@jinschoi, you say "most ruby dbi work had moved to rdb". Having trouble figuring out what this 'rdb' is you speak of. Was it a typo? Trying to figure out what my options are.

Sorry, it's called RDBI: https://github.com/RDBI

You might want to give it a try. I found it not suitable to my needs due to problems with the Oracle backend, but you may want to see if it works for you.

My repository is at https://github.com/jinschoi/ruby-dbi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment