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

Last change on this file since 948 was 948, checked in by cito, 10 months ago

Update changelog

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