source: branches/5.0.x/docs/contents/changelog.rst @ 930

Last change on this file since 930 was 930, checked in by cito, 18 months ago

Update year, version number and supported Pg versions

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