pg 1.3.5-x86-mingw32 → 1.4.2-x86-mingw32

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: 1a712a730f257c2d56f3a5d2dd14ffe938f24668f84dd2489121ac0412f9ff85
4
- data.tar.gz: 1f2d0c7ce8472465da40dae02bf4fda27519334dcccf772b9ce31961986862ed
3
+ metadata.gz: ee7a63a506afa6472f3664914858259c59caf05c9eaac6e1adf00acf453dff26
4
+ data.tar.gz: 8dfdb41d719ea6d34693ad251e2a0fd00ebd0b613ad04ef67e9d41fcf896c424
5
5
  SHA512:
6
- metadata.gz: 5215d65a832e4fef1a7dffbba41bdd4d8817f4a68d8c34060085754d9c98496df51ef34415a6c6a3de5b5b3c1b9841ae709c4bc08dec2b4b93079bb9c7baa1bd
7
- data.tar.gz: 279a731af4ff16579fd78f366cdddd6461845a480adda19072486fa7ad47519d645e9996048d5355e05690876dd48c80913e6d6f0a15c3d1d9f762d94f3ba136
6
+ metadata.gz: 96c838a5b5eaa22cf18e7f4a7d35b8572b64548b0961073b0df1f8d343292dff89671e98a01ed1aba82d98c49771d04596e029b85f767266dcbc19488e393d1b
7
+ data.tar.gz: b3fdb5f2724b35481d944db3bf87eff999daeaf33eaa86d81e66ee91b3c73825b330dc7e3586bd96a2f1c355a2394397650542adaead22a01a2cbf4157132f05
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