Re: PEP 249 Compliant error handling

2017-10-18 Thread Cameron Simpson
On 17Oct2017 21:38, Karsten Hilbert wrote: That's certainly a possibility, if that behavior conforms to the DB API "standards". My concern in this front is that in my experience working with other PEP 249 modules (specifically psycopg2), I'm pretty sure that columns

Re: PEP 249 Compliant error handling

2017-10-18 Thread Karsten Hilbert
On Wed, Oct 18, 2017 at 08:32:48AM -0800, Israel Brewster wrote: > actual question, which is "how does the STANDARD (PEP 249 in > this case) say to handle this, or, baring that (since the > standard probably doesn't explicitly say), how do the > MAJORITY of PEP 249 compliant modules handle this?"

Re: PEP 249 Compliant error handling

2017-10-18 Thread Thomas Jollans
On 17/10/17 19:26, Israel Brewster wrote: > I have written and maintain a PEP 249 compliant (hopefully) DB API for the 4D > database, and I've run into a situation where corrupted string data from the > database can cause the module to error out. Specifically, when decoding the > string, I get

Re: PEP 249 Compliant error handling

2017-10-18 Thread Israel Brewster
On Oct 17, 2017, at 12:02 PM, MRAB wrote: > > On 2017-10-17 20:25, Israel Brewster wrote: >> >>> On Oct 17, 2017, at 10:35 AM, MRAB >> > wrote: >>> >>> On 2017-10-17 18:26, Israel Brewster wrote:

Re: PEP 249 Compliant error handling

2017-10-18 Thread Israel Brewster
> On Oct 18, 2017, at 1:46 AM, Abdur-Rahmaan Janhangeer > wrote: > > all corruption systematically ignored but data piece logged in for analysis Thanks. Can you expound a bit on what you mean by "data piece logged in" in this context? I'm not aware of any logging

Re: PEP 249 Compliant error handling

2017-10-18 Thread Abdur-Rahmaan Janhangeer
all corruption systematically ignored but data piece logged in for analysis Abdur-Rahmaan Janhangeer, Mauritius abdurrahmaanjanhangeer.wordpress.com On 17 Oct 2017 21:43, "Israel Brewster" wrote: > I have written and maintain a PEP 249 compliant (hopefully) DB API for

Re: PEP 249 Compliant error handling

2017-10-17 Thread MRAB
On 2017-10-17 20:25, Israel Brewster wrote: On Oct 17, 2017, at 10:35 AM, MRAB > wrote: On 2017-10-17 18:26, Israel Brewster wrote: I have written and maintain a PEP 249 compliant (hopefully) DB API for the 4D database, and I've

Aw: Re: PEP 249 Compliant error handling

2017-10-17 Thread Karsten Hilbert
> That's certainly a possibility, if that behavior conforms to the DB API > "standards". My concern in this front is that in my experience working with > other PEP 249 modules (specifically psycopg2), I'm pretty sure that columns > designated as type VARCHAR or TEXT are returned as strings

Re: PEP 249 Compliant error handling

2017-10-17 Thread Israel Brewster
> On Oct 17, 2017, at 10:35 AM, MRAB wrote: > > On 2017-10-17 18:26, Israel Brewster wrote: >> I have written and maintain a PEP 249 compliant (hopefully) DB API for the >> 4D database, and I've run into a situation where corrupted string data from >> the database

Re: PEP 249 Compliant error handling

2017-10-17 Thread MRAB
On 2017-10-17 18:26, Israel Brewster wrote: I have written and maintain a PEP 249 compliant (hopefully) DB API for the 4D database, and I've run into a situation where corrupted string data from the database can cause the module to error out. Specifically, when decoding the string, I get a

PEP 249 Compliant error handling

2017-10-17 Thread Israel Brewster
I have written and maintain a PEP 249 compliant (hopefully) DB API for the 4D database, and I've run into a situation where corrupted string data from the database can cause the module to error out. Specifically, when decoding the string, I get a "UnicodeDecodeError: 'utf-16-le' codec can't