From anthony.tuininga at gmail.com Sat Jul 7 05:30:47 2012 From: anthony.tuininga at gmail.com (Anthony Tuininga) Date: Fri, 6 Jul 2012 21:30:47 -0600 Subject: [DB-SIG] cx_Oracle 5.1.2 Message-ID: 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 LONG_UNICODE which is a type used to handle long unicode strings. These are not explicitly supported in Oracle but can be used to bind to NCLOB, for example, without getting the error "unimplemented or unreasonable conversion requested". 2) Set the row number in a cursor when executing PL/SQL blocks as requested by Robert Ritchie. 3) Added support for setting the module, action and client_info attributes during connection so that logon triggers will see the supplied values, as requested by Rodney Barnett. In addition, binaries are now being built for Python 3.3. From anthony.tuininga at gmail.com Wed Jul 11 06:50:29 2012 From: anthony.tuininga at gmail.com (Anthony Tuininga) Date: Tue, 10 Jul 2012 22:50:29 -0600 Subject: [DB-SIG] [cx-oracle-users] cx_Oracle 5.1.2 In-Reply-To: <4FFD045E.5020602@oracle.com> References: <4FFD045E.5020602@oracle.com> Message-ID: On Tue, Jul 10, 2012 at 10:43 PM, James C. McPherson wrote: > On 7/07/12 01:30 PM, Anthony Tuininga wrote: >> >> 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. > > > Hi Anthony, > Could I clarify with you please, is it possible to build cx_Oracle > so that I can support several different versions of the rdbms from > the one cx_Oracle installation? > > ie, do I need a separate build for each 10g/11i/... version that I > want to support, or can one build support them all (assuming a certain > minimum rdbms version)? The client you use is what matters. There are some situations where the client won't work correctly with the server but they are few and far between. You should be able to pick one client and access databases of any current version (10i and 11g whether 32-bit or 64-bit) and use them with one cx_Oracle install. Hope that helps. Anthony From James.McPherson at oracle.com Wed Jul 11 06:43:10 2012 From: James.McPherson at oracle.com (James C. McPherson) Date: Wed, 11 Jul 2012 14:43:10 +1000 Subject: [DB-SIG] [cx-oracle-users] cx_Oracle 5.1.2 In-Reply-To: References: Message-ID: <4FFD045E.5020602@oracle.com> On 7/07/12 01:30 PM, Anthony Tuininga wrote: > 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. Hi Anthony, Could I clarify with you please, is it possible to build cx_Oracle so that I can support several different versions of the rdbms from the one cx_Oracle installation? ie, do I need a separate build for each 10g/11i/... version that I want to support, or can one build support them all (assuming a certain minimum rdbms version)? thanks in advance, James C. McPherson -- Oracle http://www.jmcpdotcom.com/blog From James.McPherson at oracle.com Wed Jul 11 06:52:14 2012 From: James.McPherson at oracle.com (James C. McPherson) Date: Wed, 11 Jul 2012 14:52:14 +1000 Subject: [DB-SIG] [cx-oracle-users] cx_Oracle 5.1.2 In-Reply-To: References: <4FFD045E.5020602@oracle.com> Message-ID: <4FFD067E.4090409@oracle.com> On 11/07/12 02:50 PM, Anthony Tuininga wrote: > On Tue, Jul 10, 2012 at 10:43 PM, James C. McPherson > wrote: >> On 7/07/12 01:30 PM, Anthony Tuininga wrote: >>> >>> 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. >> >> >> Hi Anthony, >> Could I clarify with you please, is it possible to build cx_Oracle >> so that I can support several different versions of the rdbms from >> the one cx_Oracle installation? >> >> ie, do I need a separate build for each 10g/11i/... version that I >> want to support, or can one build support them all (assuming a certain >> minimum rdbms version)? > > The client you use is what matters. There are some situations where > the client won't work correctly with the server but they are few and > far between. You should be able to pick one client and access > databases of any current version (10i and 11g whether 32-bit or > 64-bit) and use them with one cx_Oracle install. Hope that helps. That helps quite a lot, thankyou. James C. McPherson -- Oracle http://www.jmcpdotcom.com/blog From ethan at stoneleaf.us Wed Jul 18 00:46:07 2012 From: ethan at stoneleaf.us (Ethan Furman) Date: Tue, 17 Jul 2012 15:46:07 -0700 Subject: [DB-SIG] Foxpro goto command and deleted records Message-ID: <5005EB2F.2080906@stoneleaf.us> In Foxpro if you do a GOTO 7 with deleted off and record 7 is deleted, the record pointer doesn't move (at least in version 6). I don't like that. I see four other options: 0) don't move the pointer (listed for completeness) 1) go to that record anyway 2) go to the next undeleted record 3) go to the seventh undeleted record (possibly the least practical) 4) raise an exception Any opinions? ~Ethan~ From carl at personnelware.com Wed Jul 18 05:13:49 2012 From: carl at personnelware.com (Carl Karsten) Date: Tue, 17 Jul 2012 22:13:49 -0500 Subject: [DB-SIG] Foxpro goto command and deleted records In-Reply-To: <5005EB2F.2080906@stoneleaf.us> References: <5005EB2F.2080906@stoneleaf.us> Message-ID: On Tue, Jul 17, 2012 at 5:46 PM, Ethan Furman wrote: > In Foxpro if you do a > > GOTO 7 > > with deleted off and record 7 is deleted, the record pointer doesn't move > (at least in version 6). > > I don't like that. > > I see four other options: > > 0) don't move the pointer (listed for completeness) > 1) go to that record anyway > 2) go to the next undeleted record > 3) go to the seventh undeleted record (possibly the least practical) > 4) raise an exception > > Any opinions? dBase/FoxPro had a PURGE command which would actually de-alocate the space used for the deleted record. It also had the concept of a record pointer that related to the data on disk. Neither is at all part of the SQL spec, and I doubt has anything to do with python's dbapi. So my opinion is this isn't an issue. -- Carl K From ethan at stoneleaf.us Wed Jul 18 14:26:52 2012 From: ethan at stoneleaf.us (Ethan Furman) Date: Wed, 18 Jul 2012 05:26:52 -0700 Subject: [DB-SIG] Foxpro goto command and deleted records In-Reply-To: References: <5005EB2F.2080906@stoneleaf.us> Message-ID: <5006AB8C.9060503@stoneleaf.us> Carl Karsten wrote: > On Tue, Jul 17, 2012 at 5:46 PM, Ethan Furman wrote: >> In Foxpro if you do a >> >> GOTO 7 >> >> with deleted off and record 7 is deleted, the record pointer doesn't move >> (at least in version 6). >> >> I don't like that. >> >> I see four other options: >> >> 0) don't move the pointer (listed for completeness) >> 1) go to that record anyway >> 2) go to the next undeleted record >> 3) go to the seventh undeleted record (possibly the least practical) >> 4) raise an exception >> >> Any opinions? > > dBase/FoxPro had a PURGE command which would actually de-alocate the > space used for the deleted record. It also had the concept of a > record pointer that related to the data on disk. > > Neither is at all part of the SQL spec, and I doubt has anything to do > with python's dbapi. So my opinion is this isn't an issue. Ah, right. Forgot this list was specifically SQL based. Sorry for the noise. ~Ethan~