This project is archived and is in readonly mode.

is postgres-pr driver no longer supported? (problem with new transaction_active? method)

#988

I've noticed that recently the following method was added:


def transaction_active?
        @connection.transaction_status != PQTRANS_IDLE
end

postgres-pr doesn't have a transaction_status method. The closest I notice in the postgres-pr code is:


class ReadyForQuery < Message
  register_message_type ?Z
  fields :backend_transaction_status_indicator

  def dump
    super(1) do |buffer|
      buffer.write_byte(@backend_transaction_status_indicator)
    end
  end

  def parse(buffer)
    super do
      @backend_transaction_status_indicator = buffer.read_byte
    end
  end
end

however I can't figure out how best to use this snippet of code, I can't find anything that calls this method to see how it's used.

Reported by azimux · September 7th, 2008 @ 12:02 AM

Activity

azimux
One thing worth mentioning: I brought this up on rubyforge and learned that postgres-pr is not really being actively maintained at the moment and hasn't been for some time. So I've gone ahead and moved to ruby-postgres which is slightly annoying for a few minor reasons, but certainly doable.

So perhaps supporting postgres-pr isn't a big deal, although ruby-postgres doesn't seem to be very actively maintained either...

September 7th, 2008 @ 08:45 AM
Tarmo Tänav
- State changed from new to wontfix
ruby-pg is being maintained, and the author also maintains the old ruby-postgres gem. I guess postgres-pr is really old enough not to be worth supporting when there are so many newer alternatives.

September 18th, 2008 @ 04:20 AM
azimux
Indeed, although ruby-pg doesn't build on windows

ruby-postgres does work on windows but requires some .dll's to be copied around to use it with > 8.0 It also seems it hasn't had any changes since January

The thing that was nice about postgres-pr is it was platform independent. It's a shame postgres-pr went inactive.

September 18th, 2008 @ 06:30 AM