source: trunk/docs/contents/changelog.rst @ 940

Last change on this file since 940 was 940, checked in by cito, 14 months ago

Prepare for version 5.0.6

  • Property svn:keywords set to Author Date Id Revision
File size: 27.5 KB
Line 
1ChangeLog
2=========
3
4Vesion 5.0.6 (to be released)
5-----------------------------
6- This version officially supports the new Python 3.7.
7- Correct trove classifier for the PostgreSQL License.
8
9Version 5.0.5 (2018-04-25)
10--------------------------
11- This version officially supports the new PostgreSQL 10.
12- The memory for the string with the number of rows affected by a classic pg
13  module query() was already freed (bug report and fix by Peifeng Qiu).
14
15Version 5.0.4 (2017-07-23)
16--------------------------
17- This version officially supports the new Python 3.6 and PostgreSQL 9.6.
18- query_formatted() can now be used without parameters.
19- The automatic renaming of columns that are invalid as field names of
20  named tuples now works more accurately in Python 2.6 and 3.0.
21- Fixed error checks for unlink() and export() methods of large objects
22  (bug report by Justin Pryzby).
23- Fixed a compilation issue under OS X (bug report by Josh Johnston).
24
25Version 5.0.3 (2016-12-10)
26--------------------------
27- It is now possible to use a custom array cast function by changing
28  the type caster for the 'anyarray' type.  For instance, by calling
29  set_typecast('anyarray', lambda v, c: v) you can have arrays returned
30  as strings instead of lists.  Note that in the pg module, you can also
31  call set_array(False) in order to return arrays as strings.
32- The namedtuple classes used for the rows of query results are now cached
33  and reused internally, since creating namedtuples classes in Python is a
34  somewhat expensive operation.  By default the cache has a size of 1024
35  entries, but this can be changed with the set_row_factory_size() function.
36  In certain cases this change can notably improve the performance.
37- The namedresult() method in the classic API now also tries to rename
38  columns that would result in invalid field names.
39
40Version 5.0.2 (2016-09-13)
41--------------------------
42- Fixed an infinite recursion problem in the DB wrapper class of the classic
43  module that could occur when the underlying connection could not be properly
44  opened (bug report by Justin Pryzby).
45
46Version 5.0.1 (2016-08-18)
47--------------------------
48- The update() and delete() methods of the DB wrapper now use the OID instead
49  of the primary key if both are provided. This restores backward compatibility
50  with PyGreSQL 4.x and allows updating the primary key itself if an OID exists.
51- The connect() function of the DB API 2.0 module now accepts additional keyword
52  parameters such as "application_name" which will be passed on to PostgreSQL.
53- PyGreSQL now adapts some queries to be able to access older PostgreSQL 8.x
54  databases (as suggested on the mailing list by Andres Mejia). However, these
55  old versions of PostgreSQL are not officially supported and tested any more.
56- Fixed an issue with Postgres types that have an OID >= 0x80000000 (reported
57  on the mailing list by Justin Pryzby).
58- Allow extra values that are not used in the command in the parameter dict
59  passed to the query_formatted() method (as suggested by Justin Pryzby).
60- Improved handling of empty arrays in the classic module.
61- Unused classic connections were not properly garbage collected which could
62  cause memory leaks (reported by Justin Pryzby).
63- Made C extension compatible with MSVC 9 again (this was needed to compile for
64  Python 2 on Windows).
65
66Version 5.0 (2016-03-20)
67------------------------
68- This version now runs on both Python 2 and Python 3.
69- The supported versions are Python 2.6 to 2.7, and 3.3 to 3.5.
70- PostgreSQL is supported in all versions from 9.0 to 9.5.
71- Changes in the classic PyGreSQL module (pg):
72    - The classic interface got two new methods get_as_list() and get_as_dict()
73      returning a database table as a Python list or dict. The amount of data
74      returned can be controlled with various parameters.
75    - A method upsert() has been added to the DB wrapper class that utilizes
76      the "upsert" feature that is new in PostgreSQL 9.5. The new method nicely
77      complements the existing get/insert/update/delete() methods.
78    - When using insert/update/upsert(), you can now pass PostgreSQL arrays as
79      lists and PostgreSQL records as tuples in the classic module.
80    - Conversely, when the query method returns a PostgreSQL array, it is passed
81      to Python as a list. PostgreSQL records are converted to named tuples as
82      well, but only if you use one of the get/insert/update/delete() methods.
83      PyGreSQL uses a new fast built-in parser to achieve this.  The automatic
84      conversion of arrays to lists can be disabled with set_array(False).
85    - The pkey() method of the classic interface now returns tuples instead
86      of frozenset. The order of the tuples is like in the primary key index.
87    - Like the DB-API 2 module, the classic module now also returns bool values
88      from the database as Python bool objects instead of strings.  You can
89      still restore the old behavior by calling set_bool(False).
90    - Like the DB-API 2 module, the classic module now also returns bytea
91      data fetched from the database as byte strings, so you don't need to
92      call unescape_bytea() any more.  This has been made configurable though,
93      and you can restore the old behavior by calling set_bytea_escaped(True).
94    - A method set_jsondecode() has been added for changing or removing the
95      function that automatically decodes JSON data coming from the database.
96      By default, decoding JSON is now enabled and uses the decoder function
97      in the standard library with its default parameters.
98    - The table name that is affixed to the name of the OID column returned
99      by the get() method of the classic interface will not automatically
100      be fully qualified any more. This reduces overhead from the interface,
101      but it means you must always write the table name in the same way when
102      you call the methods using it and you are using tables with OIDs.
103      Also, OIDs are now only used when access via primary key is not possible.
104      Note that OIDs are considered deprecated anyway, and they are not created
105      by default any more in PostgreSQL 8.1 and later.
106    - The internal caching and automatic quoting of class names in the classic
107      interface has been simplified and improved, it should now perform better
108      and use less memory. Also, overhead for quoting values in the DB wrapper
109      methods has been reduced and security has been improved by passing the
110      values to libpq separately as parameters instead of inline.
111    - It is now possible to use regular type names instead of the simpler
112      type names that are used by default in PyGreSQL, without breaking any
113      of the mechanisms for quoting and typecasting, which rely on the type
114      information. This is achieved while maintaining simplicity and backward
115      compatibility by augmenting the type name string objects with all the
116      necessary information under the cover. To switch regular type names on
117      or off (this is the default), call the DB wrapper method use_regtypes().
118    - A new method query_formatted() has been added to the DB wrapper class
119      that allows using the format specifications from Python.  A flag "inline"
120      can be set to specify whether parameters should be sent to the database
121      separately or formatted into the SQL.
122    - A new type helper Bytea() has been added.
123- Changes in the DB-API 2 module (pgdb):
124    - The DB-API 2 module now always returns result rows as named tuples
125      instead of simply lists as before. The documentation explains how
126      you can restore the old behavior or use custom row objects instead.
127    - The names of the various classes used by the classic and DB-API 2
128      modules have been renamed to become simpler, more intuitive and in
129      line with the names used in the DB-API 2 documentation.
130      Since the API provides only objects of these types through constructor
131      functions, this should not cause any incompatibilities.
132    - The DB-API 2 module now supports the callproc() cursor method. Note
133      that output parameters are currently not replaced in the return value.
134    - The DB-API 2 module now supports copy operations between data streams
135      on the client and database tables via the COPY command of PostgreSQL.
136      The cursor method copy_from() can be used to copy data from the database
137      to the client, and the cursor method copy_to() can be used to copy data
138      from the client to the database.
139    - The 7-tuples returned by the description attribute of a pgdb cursor
140      are now named tuples, i.e. their elements can be also accessed by name.
141      The column names and types can now also be requested through the
142      colnames and coltypes attributes, which are not part of DB-API 2 though.
143      The type_code provided by the description attribute is still equal to
144      the PostgreSQL internal type name, but now carries some more information
145      in additional attributes. The size, precision and scale information that
146      is part of the description is now properly set for numeric types.
147    - If you pass a Python list as one of the parameters to a DB-API 2 cursor,
148      it is now automatically bound using an ARRAY constructor. If you pass a
149      Python tuple, it is bound using a ROW constructor. This is useful for
150      passing records as well as making use of the IN syntax.
151    - Inversely, when a fetch method of a DB-API 2 cursor returns a PostgreSQL
152      array, it is passed to Python as a list, and when it returns a PostgreSQL
153      composite type, it is passed to Python as a named tuple. PyGreSQL uses
154      a new fast built-in parser to achieve this. Anonymous composite types are
155      also supported, but yield only an ordinary tuple containing text strings.
156    - New type helpers Interval() and Uuid() have been added.
157    - The connection has a new attribute "closed" that can be used to check
158      whether the connection is closed or broken.
159    - SQL commands are always handled as if they include parameters, i.e.
160      literal percent signs must always be doubled. This consistent behavior
161      is necessary for using pgdb with wrappers like SQLAlchemy.
162    - PyGreSQL 5.0 will be supported as a database driver by SQLAlchemy 1.1.
163- Changes concerning both modules:
164    - PyGreSQL now tries to raise more specific and appropriate subclasses of
165      DatabaseError than just ProgrammingError. Particularly, when database
166      constraints are violated, it raises an IntegrityError now.
167    - The modules now provide get_typecast() and set_typecast() methods
168      allowing to control the typecasting on the global level.  The connection
169      objects have got type caches with the same methods which give control
170      over the typecasting on the level of the current connection.
171      See the documentation on details about the type cache and the typecast
172      mechanisms provided by PyGreSQL.
173    - Dates, times, timestamps and time intervals are now returned as the
174      corresponding Python objects from the datetime module of the standard
175      library.  In earlier versions of PyGreSQL they had been returned as
176      strings.  You can restore the old behavior by deactivating the respective
177      typecast functions, e.g. set_typecast('date', str).
178    - PyGreSQL now support the "uuid" data type, converting such columns
179      automatically to and from Python uuid.UUID objects.
180    - PyGreSQL now supports the "hstore" data type, converting such columns
181      automatically to and from Python dictionaries.  If you want to insert
182      Python objects as JSON data using DB-API 2, you should wrap them in the
183      new HStore() type constructor as a hint to PyGreSQL.
184    - PyGreSQL now supports the "json" and "jsonb" data types, converting such
185      columns automatically to and from Python objects. If you want to insert
186      Python objects as JSON data using DB-API 2, you should wrap them in the
187      new Json() type constructor as a hint to PyGreSQL.
188    - A new type helper Literal() for inserting parameters literally as SQL
189      has been added.  This is useful for table names, for instance.
190    - Fast parsers cast_array(), cast_record() and cast_hstore for the input
191      and output syntax for PostgreSQL arrays, composite types and the hstore
192      type have been added to the C extension module. The array parser also
193      allows using multi-dimensional arrays with PyGreSQL.
194    - The tty parameter and attribute of database connections has been
195      removed since it is not supported any more since PostgreSQL 7.4.
196
197Version 4.2.2 (2016-03-18)
198--------------------------
199- The get_relations() and get_tables() methods now also return system views
200  and tables if you set the optional "system" parameter to True.
201- Fixed a regression when using temporary tables with DB wrapper methods
202  (thanks to Patrick TJ McPhee for reporting).
203
204Version 4.2.1 (2016-02-18)
205--------------------------
206- Fixed a small bug when setting the notice receiver.
207- Some more minor fixes and re-packaging with proper permissions.
208
209Version 4.2 (2016-01-21)
210------------------------
211- The supported Python versions are 2.4 to 2.7.
212- PostgreSQL is supported in all versions from 8.3 to 9.5.
213- Set a better default for the user option "escaping-funcs".
214- Force build to compile with no errors.
215- New methods get_parameters() and set_parameters() in the classic interface
216  which can be used to get or set run-time parameters.
217- New method truncate() in the classic interface that can be used to quickly
218  empty a table or a set of tables.
219- Fix decimal point handling.
220- Add option to return boolean values as bool objects.
221- Add option to return money values as string.
222- get_tables() does not list information schema tables any more.
223- Fix notification handler (Thanks Patrick TJ McPhee).
224- Fix a small issue with large objects.
225- Minor improvements of the NotificationHandler.
226- Converted documentation to Sphinx and added many missing parts.
227- The tutorial files have become a chapter in the documentation.
228- Greatly improved unit testing, tests run with Python 2.4 to 2.7 again.
229
230Version 4.1.1 (2013-01-08)
231--------------------------
232- Add NotificationHandler class and method.  Replaces need for pgnotify.
233- Sharpen test for inserting current_timestamp.
234- Add more quote tests.  False and 0 should evaluate to NULL.
235- More tests - Any number other than 0 is True.
236- Do not use positional parameters internally.
237  This restores backward compatibility with version 4.0.
238- Add methods for changing the decimal point.
239
240Version 4.1 (2013-01-01)
241------------------------
242- Dropped support for Python below 2.5 and PostgreSQL below 8.3.
243- Added support for Python up to 2.7 and PostgreSQL up to 9.2.
244- Particularly, support PQescapeLiteral() and PQescapeIdentifier().
245- The query method of the classic API now supports positional parameters.
246  This an effective way to pass arbitrary or unknown data without worrying
247  about SQL injection or syntax errors (contribution by Patrick TJ McPhee).
248- The classic API now supports a method namedresult() in addition to
249  getresult() and dictresult(), which returns the rows of the result
250  as named tuples if these are supported (Python 2.6 or higher).
251- The classic API has got the new methods begin(), commit(), rollback(),
252  savepoint() and release() for handling transactions.
253- Both classic and DBAPI 2 connections can now be used as context
254  managers for encapsulating transactions.
255- The execute() and executemany() methods now return the cursor object,
256  so you can now write statements like "for row in cursor.execute(...)"
257  (as suggested by Adam Frederick).
258- Binary objects are now automatically escaped and unescaped.
259- Bug in money quoting fixed.  Amounts of $0.00 handled correctly.
260- Proper handling of date and time objects as input.
261- Proper handling of floats with 'nan' or 'inf' values as input.
262- Fixed the set_decimal() function.
263- All DatabaseError instances now have a sqlstate attribute.
264- The getnotify() method can now also return payload strings (#15).
265- Better support for notice processing with the new methods
266  set_notice_receiver() and get_notice_receiver()
267  (as suggested by Michael Filonenko, see #37).
268- Open transactions are rolled back when pgdb connections are closed
269  (as suggested by Peter Harris, see #46).
270- Connections and cursors can now be used with the "with" statement
271  (as suggested by Peter Harris, see #46).
272- New method use_regtypes() that can be called to let getattnames()
273  return regular type names instead of the simplified classic types (#44).
274
275Version 4.0 (2009-01-01)
276------------------------
277- Dropped support for Python below 2.3 and PostgreSQL below 7.4.
278- Improved performance of fetchall() for large result sets
279  by speeding up the type casts (as suggested by Peter Schuller).
280- Exposed exceptions as attributes of the connection object.
281- Exposed connection as attribute of the cursor object.
282- Cursors now support the iteration protocol.
283- Added new method to get parameter settings.
284- Added customizable row_factory as suggested by Simon Pamies.
285- Separated between mandatory and additional type objects.
286- Added keyword args to insert, update and delete methods.
287- Added exception handling for direct copy.
288- Start transactions only when necessary, not after every commit().
289- Release the GIL while making a connection
290  (as suggested by Peter Schuller).
291- If available, use decimal.Decimal for numeric types.
292- Allow DB wrapper to be used with DB-API 2 connections
293  (as suggested by Chris Hilton).
294- Made private attributes of DB wrapper accessible.
295- Dropped dependence on mx.DateTime module.
296- Support for PQescapeStringConn() and PQescapeByteaConn();
297  these are now also used by the internal _quote() functions.
298- Added 'int8' to INTEGER types. New SMALLINT type.
299- Added a way to find the number of rows affected by a query()
300  with the classic pg module by returning it as a string.
301  For single inserts, query() still returns the oid as an integer.
302  The pgdb module already provides the "rowcount" cursor attribute
303  for the same purpose.
304- Improved getnotify() by calling PQconsumeInput() instead of
305  submitting an empty command.
306- Removed compatibility code for old OID munging style.
307- The insert() and update() methods now use the "returning" clause
308  if possible to get all changed values, and they also check in advance
309  whether a subsequent select is possible, so that ongoing transactions
310  won't break if there is no select privilege.
311- Added "protocol_version" and "server_version" attributes.
312- Revived the "user" attribute.
313- The pg module now works correctly with composite primary keys;
314  these are represented as frozensets.
315- Removed the undocumented and actually unnecessary "view" parameter
316  from the get() method.
317- get() raises a nicer ProgrammingError instead of a KeyError
318  if no primary key was found.
319- delete() now also works based on the primary key if no oid available
320  and returns whether the row existed or not.
321
322Version 3.8.1 (2006-06-05)
323--------------------------
324- Use string methods instead of deprecated string functions.
325- Only use SQL-standard way of escaping quotes.
326- Added the functions escape_string() and escape/unescape_bytea()
327  (as suggested by Charlie Dyson and Kavous Bojnourdi a long time ago).
328- Reverted code in clear() method that set date to current.
329- Added code for backwards compatibility in OID munging code.
330- Reorder attnames tests so that "interval" is checked for before "int."
331- If caller supplies key dictionary, make sure that all has a namespace.
332
333Version 3.8 (2006-02-17)
334------------------------
335- Installed new favicon.ico from Matthew Sporleder <mspo@mspo.com>
336- Replaced snprintf by PyOS_snprintf.
337- Removed NO_SNPRINTF switch which is not needed any longer
338- Clean up some variable names and namespace
339- Add get_relations() method to get any type of relation
340- Rewrite get_tables() to use get_relations()
341- Use new method in get_attnames method to get attributes of views as well
342- Add Binary type
343- Number of rows is now -1 after executing no-result statements
344- Fix some number handling
345- Non-simple types do not raise an error any more
346- Improvements to documentation framework
347- Take into account that nowadays not every table must have an oid column
348- Simplification and improvement of the inserttable() function
349- Fix up unit tests
350- The usual assortment of minor fixes and enhancements
351
352Version 3.7 (2005-09-07)
353------------------------
354Improvement of pgdb module:
355
356- Use Python standard `datetime` if `mxDateTime` is not available
357
358Major improvements and clean-up in classic pg module:
359
360- All members of the underlying connection directly available in `DB`
361- Fixes to quoting function
362- Add checks for valid database connection to methods
363- Improved namespace support, handle `search_path` correctly
364- Removed old dust and unnecessary imports, added docstrings
365- Internal sql statements as one-liners, smoothed out ugly code
366
367Version 3.6.2 (2005-02-23)
368--------------------------
369- Further fixes to namespace handling
370
371Version 3.6.1 (2005-01-11)
372--------------------------
373- Fixes to namespace handling
374
375Version 3.6 (2004-12-17)
376------------------------
377- Better DB-API 2.0 compliance
378- Exception hierarchy moved into C module and made available to both APIs
379- Fix error in update method that caused false exceptions
380- Moved to standard exception hierarchy in classic API
381- Added new method to get transaction state
382- Use proper Python constants where appropriate
383- Use Python versions of strtol, etc. Allows Win32 build.
384- Bug fixes and cleanups
385
386Version 3.5 (2004-08-29)
387------------------------
388Fixes and enhancements:
389
390- Add interval to list of data types
391- fix up method wrapping especially close()
392- retry pkeys once if table missing in case it was just added
393- wrap query method separately to handle debug better
394- use isinstance instead of type
395- fix free/PQfreemem issue - finally
396- miscellaneous cleanups and formatting
397
398Version 3.4 (2004-06-02)
399------------------------
400Some cleanups and fixes.
401This is the first version where PyGreSQL is moved back out of the
402PostgreSQL tree. A lot of the changes mentioned below were actually
403made while in the PostgreSQL tree since their last release.
404
405- Allow for larger integer returns
406- Return proper strings for true and false
407- Cleanup convenience method creation
408- Enhance debugging method
409- Add reopen method
410- Allow programs to preload field names for speedup
411- Move OID handling so that it returns long instead of int
412- Miscellaneous cleanups and formatting
413
414Version 3.3 (2001-12-03)
415------------------------
416A few cleanups.  Mostly there was some confusion about the latest version
417and so I am bumping the number to keep it straight.
418
419- Added NUMERICOID to list of returned types. This fixes a bug when
420  returning aggregates in the latest version of PostgreSQL.
421
422Version 3.2 (2001-06-20)
423------------------------
424Note that there are very few changes to PyGreSQL between 3.1 and 3.2.
425The main reason for the release is the move into the PostgreSQL
426development tree.  Even the WIN32 changes are pretty minor.
427
428- Add Win32 support (gerhard@bigfoot.de)
429- Fix some DB-API quoting problems (niall.smart@ebeon.com)
430- Moved development into PostgreSQL development tree.
431
432Version 3.1 (2000-11-06)
433------------------------
434- Fix some quoting functions.  In particular handle NULLs better.
435- Use a method to add primary key information rather than direct
436  manipulation of the class structures
437- Break decimal out in `_quote` (in pg.py) and treat it as float
438- Treat timestamp like date for quoting purposes
439- Remove a redundant SELECT from the `get` method speeding it,
440  and `insert` (since it calls `get`) up a little.
441- Add test for BOOL type in typecast method to `pgdbTypeCache` class
442  (tv@beamnet.de)
443- Fix pgdb.py to send port as integer to lower level function
444  (dildog@l0pht.com)
445- Change pg.py to speed up some operations
446- Allow updates on tables with no primary keys
447
448Version 3.0 (2000-05-30)
449------------------------
450- Remove strlen() call from pglarge_write() and get size from object
451  (Richard@Bouska.cz)
452- Add a little more error checking to the quote function in the wrapper
453- Add extra checking in `_quote` function
454- Wrap query in pg.py for debugging
455- Add DB-API 2.0 support to pgmodule.c (andre@via.ecp.fr)
456- Add DB-API 2.0 wrapper pgdb.py (andre@via.ecp.fr)
457- Correct keyword clash (temp) in tutorial
458- Clean up layout of tutorial
459- Return NULL values as None (rlawrence@lastfoot.com)
460  (WARNING: This will cause backwards compatibility issues)
461- Change None to NULL in insert and update
462- Change hash-bang lines to use /usr/bin/env
463- Clearing date should be blank (NULL) not TODAY
464- Quote backslashes in strings in `_quote` (brian@CSUA.Berkeley.EDU)
465- Expanded and clarified build instructions (tbryan@starship.python.net)
466- Make code thread safe (Jerome.Alet@unice.fr)
467- Add README.distutils (mwa@gate.net & jeremy@cnri.reston.va.us)
468- Many fixes and increased DB-API compliance by chifungfan@yahoo.com,
469  tony@printra.net, jeremy@alum.mit.edu and others to get the final
470  version ready to release.
471
472Version 2.4 (1999-06-15)
473------------------------
474- Insert returns None if the user doesn't have select permissions
475  on the table.  It can (and does) happen that one has insert but
476  not select permissions on a table.
477- Added ntuples() method to query object (brit@druid.net)
478- Corrected a bug related to getresult() and the money type
479- Corrected a bug related to negative money amounts
480- Allow update based on primary key if munged oid not available and
481  table has a primary key
482- Add many __doc__ strings (andre@via.ecp.fr)
483- Get method works with views if key specified
484
485Version 2.3 (1999-04-17)
486------------------------
487- connect.host returns "localhost" when connected to Unix socket
488  (torppa@tuhnu.cutery.fi)
489- Use `PyArg_ParseTupleAndKeywords` in connect() (torppa@tuhnu.cutery.fi)
490- fixes and cleanups (torppa@tuhnu.cutery.fi)
491- Fixed memory leak in dictresult() (terekhov@emc.com)
492- Deprecated pgext.py - functionality now in pg.py
493- More cleanups to the tutorial
494- Added fileno() method - terekhov@emc.com (Mikhail Terekhov)
495- added money type to quoting function
496- Compiles cleanly with more warnings turned on
497- Returns PostgreSQL error message on error
498- Init accepts keywords (Jarkko Torppa)
499- Convenience functions can be overridden (Jarkko Torppa)
500- added close() method
501
502Version 2.2 (1998-12-21)
503------------------------
504- Added user and password support thanks to Ng Pheng Siong (ngps@post1.com)
505- Insert queries return the inserted oid
506- Add new `pg` wrapper (C module renamed to _pg)
507- Wrapped database connection in a class
508- Cleaned up some of the tutorial.  (More work needed.)
509- Added `version` and `__version__`.
510  Thanks to thilo@eevolute.com for the suggestion.
511
512Version 2.1 (1998-03-07)
513------------------------
514- return fields as proper Python objects for field type
515- Cleaned up pgext.py
516- Added dictresult method
517
518Version 2.0  (1997-12-23)
519-------------------------
520- Updated code for PostgreSQL 6.2.1 and Python 1.5
521- Reformatted code and converted to use full ANSI style prototypes
522- Changed name to PyGreSQL (from PyGres95)
523- Changed order of arguments to connect function
524- Created new type `pgqueryobject` and moved certain methods to it
525- Added a print function for pgqueryobject
526- Various code changes - mostly stylistic
527
528Version 1.0b (1995-11-04)
529-------------------------
530- Keyword support for connect function moved from library file to C code
531  and taken away from library
532- Rewrote documentation
533- Bug fix in connect function
534- Enhancements in large objects interface methods
535
536Version 1.0a (1995-10-30)
537-------------------------
538A limited release.
539
540- Module adapted to standard Python syntax
541- Keyword support for connect function in library file
542- Rewrote default parameters interface (internal use of strings)
543- Fixed minor bugs in module interface
544- Redefinition of error messages
545
546Version 0.9b (1995-10-10)
547-------------------------
548The first public release.
549
550- Large objects implementation
551- Many bug fixes, enhancements, ...
552
553Version 0.1a (1995-10-07)
554-------------------------
555- Basic libpq functions (SQL access)
Note: See TracBrowser for help on using the repository browser.