From anthony.tuininga at gmail.com  Wed Jul 21 06:05:13 2010
From: anthony.tuininga at gmail.com (Anthony Tuininga)
Date: Tue, 20 Jul 2010 22:05:13 -0600
Subject: [DB-SIG] cx_Oracle 5.0.4
Message-ID: <AANLkTimUv_7XJ0lul-PC1r4wPyuXFlm28_SUb5-YaaJE@mail.gmail.com>

What is cx_Oracle?

cx_Oracle is a Python extension module that allows access to Oracle and
conforms to the Python database API 2.0 specifications with a few
exceptions.


Where do I get it?

http://cx-oracle.sourceforge.net


What's new?

1) Added support for Python 2.7.

2) Added support for new parameter (port) for subscription() call
which allows the client to specify the listening port for callback
notifications from the database server. Thanks to Geoffrey Weber for
the initial patch.

3) Fixed compilation under Oracle 9i.

4) Fixed a few error messages.

From anthony.tuininga at gmail.com  Fri Jul 23 06:55:25 2010
From: anthony.tuininga at gmail.com (Anthony Tuininga)
Date: Thu, 22 Jul 2010 22:55:25 -0600
Subject: [DB-SIG] cx_OracleDBATools 3.0
Message-ID: <AANLkTillGv_0o4frPEJUnWnas2dxfZOzNA4QrTrhMH44@mail.gmail.com>

What is cx_OracleDBATools?

cx_OracleDBATools is a set of Python scripts that handle Oracle DBA
tasks in a cross platform manner. These scripts are intended to work the
same way on all platforms and hide the complexities involved in managing
Oracle databases, especially on Windows. Binaries are provided for those
who do not have a Python installation.


Where do I get it?

http://cx-oradbatools.sourceforge.net


What's new?

1) Added support for Oracle 11.x.

2) Removed direct support for Oracle 8.x and Oracle 9.x which are no
longer supported by Oracle.

3) Write all SQL used for creating or restoring the database to the
file system to allow for manual recovery in case of failures.

4) Added new script for exporting the parameter file as a means of
testing the contents of the generated parameter file or for seeing the
contents of the stored parameter file if one is being used.

5) Fixed handling of parameter log_archive_duplex_dest.

6) Fixed hanlding of parameters with a blank value.

7) Workaround bug in Python on Linux where os.waitpid() results in an
OS error about no child processes.

8) Make source compatible with Python 3.x without losing compatibility
with Python 2.x.

9) Changed backup and restore to use RMAN which allows for backups
while the database is running. The backup utility can now create
directories, uncompressed tar files or tar files compressed with
either gzip or bzip2 as desired. Server parameter files (spfiles) and
password files are now backed up correctly.

10) On Windows, configuration is now read from the service directly
and the situation where the database is configured to start when the
service starts is now handled correctly.

11) Created build configuration script using the new version of
cx_Freeze which allows for building installer images on Windows and
RPM packages on Linux.

12) Added documentation.

13) The cx_Logging module is now used for all logging instead of
simply being printed to stdout or stderr.

From tparakkal at ClearPractice.com  Thu Jul 29 20:24:44 2010
From: tparakkal at ClearPractice.com (Thajib Parakkal)
Date: Thu, 29 Jul 2010 13:24:44 -0500
Subject: [DB-SIG] cx_Oracle on Oracle 9.2 Import Error
Message-ID: <9afd9803-a823-4896-a0f7-dd2311c212ad@ClearPractice.com>



Hello,
  I have a similar problem when I tried to usecx_Oracle on a Windows Server 2003 Standard Edition. I have Oracle 9.2 clientinstalled. 
I get : 
Traceback (most recent call last):
  File "<pyshell#0>", line 1, in<module>
    import cx_Oracle
ImportError: DLL load failed: The specified procedure couldnot be found.
 
Python version 2.7 installed
And I installed the  cx_Oracle 5.0.4 11g for Py 2.7
 
This is the same I have on my laptop and the server.
 
On my Laptop with Windows XP and Oracle 11g clienteverything is good. I have the script which I prepared on my laptop and had todeploy in the server which has Oracle 9i, that?s where its having trouble!!
What do you suggest?
 
Thanks,
Thajib
 




This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may contain confidential health information that is legally privileged. The information is intended only for the use of the individual or entity named above. The authorized recipient of this transmission is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to delete or destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited. If you have received this E-mail in error, please notify the sender and delete this message immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/db-sig/attachments/20100729/e3747a2f/attachment.html>

From vernondcole at gmail.com  Sat Jul 31 09:53:23 2010
From: vernondcole at gmail.com (Vernon Cole)
Date: Sat, 31 Jul 2010 01:53:23 -0600
Subject: [DB-SIG] Announcing adodbapi version 2.4.0 -- it has COLUMN NAME
	data access
Message-ID: <AANLkTimpFKgix0i45B3AsbOy3=YmZZOaOeH0c1bj5Za-@mail.gmail.com>

Announcing a new version of adodbapi...

[ for those who may not know...
[ adodbapi is a pure Python package which fully implements the PEP-249
db-api
[ using Microsoft ADO/db on Windows.
[ It runs on CPython versions 2.3 and later, IronPython 2.6 and later,
[ or Python 3.0 and later.

I have often been frustrated by the need to count '?' marks for input
parameters
and remembering column numbers to get my SQL output.
This release fixes that by allowing the use of 'named' parameters as an
option,
and by returning 'SQLrow' objects which allow the use of column names.

This version includes a distutils setup.py file, so installation is easy.
It even runs 2to3 automatically if you run it using a 3.n Python.
(Why didn't I do this years ago?)

Here's what's new............................

* adodbapi version 2.4.0 -- in this version,
   "fetchall()" and "fetchmany()" return an SQLrows object
   ...which emulates a sequence of SQLrow objects.
   "fetchone()" or the cursor's "next()" method return an SQLrow object.
   An SQLrow object emulates a tuple of data fields.
   An SQLrow object also appears to have an attribute for each column of
data.
   therefore...
   >>> import adodbapi
   >>> myConnection = adodbapi.connection('someDSN')
   >>> cur = myConnection.cursor()
   >>> cur.execute("select name, rank, serialNumber from soldiers")
   >>> row = cur.fetchone()
   >>> assert row[0] == row['name']
   >>> assert row[1] == row.rank
   >>> rows = cur.fecthall()
   >>> assert rows[4,'serialNumber'] == rows[4][2]

* adodbapi version 2.3.0 -- this is includes major refactoring and
   specifically adds features for django support, including the ability for
the
   programmer to change ado's SQL "paramstyle" at run time to select between
   'qmark', 'format' and 'named' methods of passing SQL parameters.
** also, in response to user requests, adodbapi will now use client-side
   cursors by default.  This will make rowcount and stored procedure return
   parameter values more readily available.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/db-sig/attachments/20100731/11f377bd/attachment.html>