pg 1.3.5 → 1.4.2

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 0bb3782224d0c471417ceaa47d1355d5a06be2590fb3671fde73882346db0c5c
4
- data.tar.gz: cd728b238d0b174f02a31c38afbd990177f81eec8516a1c953ee7bade1ddb4c6
3
+ metadata.gz: 8fe333d872d6b92992e5e25bf9cbcef4ca5a1b6d80d844d71f65bd3e4939a318
4
+ data.tar.gz: 5befd787deeb31a87ff578f64b88b793337d05c2c09a3b11b94acbb140ea9718
5
5
  SHA512:
6
- metadata.gz: d7b3ad8293281fb830274dc0e3d6e3c59c1dca85ea4f112f0aaf3a7629f61e315747f1e6ecad96e7a9528d42eeb3baafb819b7360d02acfc636ae7cb2d24ef42
7
- data.tar.gz: f2476f2c7b1950346adf87c3675b838b9c57c909d6d787b50f4cf418ccb51296a02677faac7910378a665daa087f2aa552375f72ca42ba428e539cf07e80392c
6
+ metadata.gz: 4ce4ae607591a8b549a4443e3531e3c538ddcfaf3da40478e30fc04413f7864dc52d95ae3a7e94b3891adfd384e44474e0a8035f6e9b7be2f19143c5d9150657
7
+ data.tar.gz: 4f74125642ee9ed370b679703fac32d286732d27001b66af5c09460f054b0729a5c19d31e449b3807d4d6176e803e63d1d32a6bd1944ee0a34ff3c4527836c2a
checksums.yaml.gz.sig CHANGED
Binary file
data/History.rdoc CHANGED
@@ -1,3 +1,43 @@
1
+ == v1.4.2 [2022-07-27] Lars Kanis <lars@greiz-reinsdorf.de>
2
+
3
+ Bugfixes:
4
+
5
+ - Properly handle empty host parameter when connecting. #471
6
+ - Update Windows fat binary gem to OpenSSL-1.1.1q.
7
+
8
+
9
+ == v1.4.1 [2022-06-24] Lars Kanis <lars@greiz-reinsdorf.de>
10
+
11
+ Bugfixes:
12
+
13
+ - Fix another ruby-2.7 keyword warning. #465
14
+ - Allow PG::Error to be created without arguments. #466
15
+
16
+
17
+ == v1.4.0 [2022-06-20] Lars Kanis <lars@greiz-reinsdorf.de>
18
+
19
+ Added:
20
+
21
+ - Add PG::Connection#hostaddr, present since PostgreSQL-12. #453
22
+ - Add PG::Connection.conninfo_parse to wrap PQconninfoParse. #453
23
+
24
+ Bugfixes:
25
+
26
+ - Try IPv6 and IPv4 addresses, if DNS resolves to both. #452
27
+ - Re-add block-call semantics to PG::Connection.new accidently removed in pg-1.3.0. #454
28
+ - Handle client error after all data consumed in #copy_data for output. #455
29
+ - Avoid spurious keyword argument warning on Ruby 2.7. #456
30
+ - Change connection setup to respect connect_timeout parameter. #459
31
+ - Fix indefinite hang in case of connection error on Windows #458
32
+ - Set connection attribute of PG::Error in various places where it was missing. #461
33
+ - Fix transaction leak on early break/return. #463
34
+ - Update Windows fat binary gem to OpenSSL-1.1.1o and PostgreSQL-14.4.
35
+
36
+ Enhancements:
37
+
38
+ - Don't flush at each put_copy_data call, but flush at get_result. #462
39
+
40
+
1
41
  == v1.3.5 [2022-03-31] Lars Kanis <lars@greiz-reinsdorf.de>
2
42
 
3
43
  Bugfixes:
data/Rakefile.cross CHANGED
@@ -31,8 +31,8 @@ class CrossLibrary < OpenStruct
31
31
  self.host_platform = toolchain
32
32
 
33
33
  # Cross-compilation constants
34
- self.openssl_version = ENV['OPENSSL_VERSION'] || '1.1.1m'
35
- self.postgresql_version = ENV['POSTGRESQL_VERSION'] || '14.2'
34
+ self.openssl_version = ENV['OPENSSL_VERSION'] || '1.1.1q'
35
+ self.postgresql_version = ENV['POSTGRESQL_VERSION'] || '14.4'
36
36
 
37
37
  # Check if symlinks work in the current working directory.
38
38
  # This fails, if rake-compiler-dock is running on a Windows box.
data/ext/extconf.rb CHANGED
@@ -1,5 +1,3 @@
1
- # -*- encoding: utf-8 -*-
2
-
3
1
  require 'pp'
4
2
  require 'mkmf'
5
3
 
@@ -169,32 +167,3 @@ end
169
167
  create_header()
170
168
  create_makefile( "pg_ext" )
171
169
 
172
-
173
- def message!(important_message)
174
- message important_message
175
- if !$stdout.tty? && File.chardev?('/dev/tty')
176
- File.open('/dev/tty', 'w') do |tty|
177
- tty.print important_message
178
- end
179
- end
180
- rescue
181
- end
182
-
183
- if "2022-04-01" == Time.now.strftime("%Y-%m-%d")
184
- message! <<-EOM
185
- ===================================================================
186
- HEADS UP! Prepare for pg-1.4.2022 ! 🎉🎉🎉
187
-
188
- Now that psycopg3 has most of the features of ruby-pg, we plan to
189
- switch to using it as our foundation for the next pg release.
190
- It will run through pycall and requires a working python setup.
191
- This will minimize our development and maintenance efforts, since
192
- it allows us to use one and the same code base for both programming
193
- languages - ruby and python. 👏😃
194
-
195
- And we follow the recent merge of the Django and Rails teams! ❤️
196
-
197
- Stay up-to-date at https://github.com/ged/ruby-pg/issues/449
198
- ===================================================================
199
- EOM
200
- end