Control: tags -1 + moreinfo

Hi Andrey,

I'm trying to reproduce your issue but I can't seem to be able to.

I get an error the 1st time I try to establish the connection but I
believe that's linked to something else.

Here's what I see (I use docker run --rm --name pg-docker -e
POSTGRES_PASSWORD=docker -d -p5432:5432 postgres so don't really care
that there's a password here, it's going to be gone in a min):

$ irb
irb(main):001:0> require 'pg'
=> true
irb(main):002:0> require 'sequel'
=> true
irb(main):003:0> DB =
Sequel.connect('postgres://postgres:docker@localhost:5432/postgres')
Traceback (most recent call last):
       12: from /usr/bin/irb:11:in `<main>'
       11: from (irb):3
       10: from /usr/lib/ruby/vendor_ruby/sequel/core.rb:121:in `connect'
        9: from
/usr/lib/ruby/vendor_ruby/sequel/database/connecting.rb:36:in
`connect'
        8: from
/usr/lib/ruby/vendor_ruby/sequel/database/connecting.rb:17:in
`adapter_class'
        7: from
/usr/lib/ruby/vendor_ruby/sequel/database/connecting.rb:88:in
`load_adapter'
        6: from
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
        5: from
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
        4: from
/usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:803:in `<top
(required)>'
        3: from
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
        2: from
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
        1: from
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`const_get'
NameError (uninitialized constant PGError)
Did you mean?  TypeError
irb(main):004:0> DB =
Sequel.connect('postgres://postgres:docker@localhost:5432/postgres')
=> #<Sequel::Postgres::Database:
"postgres://postgres:docker@localhost:5432/postgres">
irb(main):005:0> DB.run("create table events (a text, b text)")
=> nil
irb(main):006:0> DB[:events].insert('foo', 'bar')
=> nil
irb(main):007:0> DB[:events].insert('foo1', '1bar')
=> nil
irb(main):008:0> DB[:events].insert('foo2', '2bar')
=> nil
irb(main):009:0> DB[:events].insert('foo3', '3bar')
=> nil
irb(main):010:0> DB[:events].insert('foo4', '4bar')
=> nil
irb(main):011:0> DB[:events].insert('foo5', '5bar')
=> nil
irb(main):012:0> DB[:events].insert('foo6', '6bar')
=> nil
irb(main):013:0> DB[:events].first
=> {:a=>"foo", :b=>"bar"}
irb(main):014:0> DB[:events].delete
=> 7
irb(main):015:0> DB.run("drop table events")
=> nil
irb(main):016:0>

So I wonder if that's really related to ruby-sequel-pg.
The other packages I got are:
$ dpkg -l | grep 'ruby-sequel\|ruby-pg\|ruby  '
ii  ruby                                    1:2.5.1
          amd64        Interpreter of object-oriented scripting
language Ruby (default version)
ii  ruby-pg                                 1.1.3-3
          amd64        PostgreSQL interface for Ruby
ii  ruby-sequel                             5.15.0-1
          all          Simple, flexible, and powerful SQL database
access toolkit for Ruby
ii  ruby-sequel-pg                          1.6.16-1+b2
          amd64        Faster SELECTs when using Sequel with pg


Can you try to reproduce it with your current version of packages and
let us know if you still see the issue please?

Thanks for your help,
Joseph
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE6CPaER4i14V+HYZYY/eACiPXslIFAl0Bf88ACgkQY/eACiPX
slJHLw//YLPbLaDuxa+BkwmJrX5HULj1D1EKBkcuFZLD0sECKbMMDxgggNz90Fxu
/Ns3Rrv06Y+aedS56MPDlwaLdlW29w2ea81ZDly8ycA6v7mLKvmDfog5K5XGAGmD
X4PN+cPsItI5KFF8yWjyhcNoY+AJjVZQSAi0euzNtQYRA3dtfkgMWYdxMBj8l2ZT
ISmv8ETgZTpv0phhOlSSrXxgWLa1KuN3Bttt0qUdc+/6IQ9Zxi6QfuDTzdec0yZU
k2fhGaOEVcva5twM7T86r+PE5ucxtTWs3HGo/anCdVU4ZPM3jxUeJILLDUIyQ62M
BJqJgNnJHGVv8YYHfh9aFB0U2u4eqVSr54hiIeixCsDs/n63QuoxSu8mpSu3KfwB
cQvqZm7hb7LSKT8Tqvhndcnsa3Q6ScceX5DZebS620iElmxOVH+5vL+ONcbCWf7C
OWN6bsO9XAOvUfsiDU+i4Fdpi3PNPpH3nPHvHPigzA8ZRW7892vhjB/2qFt9k9T5
iNnzeJM/4uRfPg8qkeqjR8Tw7opBqTiFOpW6wnPRY6/7AuGAbAr0JufY9MTf9O5T
e4yysbJmNHWgRn4pc+Ht0Mv6p1a+UKKg4xxGxs6uaCmermRrM4dPb4aFDElahsUA
+7D9ITtpV8MhMswKbDeoEsCX7GJSWR+AAl5lyFOKHJcaa8eaqJk=
=i0V2
-----END PGP SIGNATURE-----

Reply via email to