I am authoring a dialect for our database technology and one of the tests
is failing, but I am not quite sure why, or how to proceed.
Would someone know where I'd look, or what I may be missing, to fix this
aspect of the dialect?
I am likely missing something, but I've already messed with the
On Tuesday, May 12, 2015 at 10:06:57 AM UTC-5, Michael Bayer wrote:
On 5/12/15 9:34 AM, Jonathon Nelson wrote:
I'm working on an application where I want to use one and only one
connection, even in the face of errors.
Originally I used AssertionPool, but it seemed to misbehave
I got it working. The second example was really helpful. Thanks, Mike!
Best regards,
Bruno
On Wed, May 13, 2015 at 3:15 PM, Mike Bayer mike...@zzzcomputing.com
wrote:
On 5/13/15 5:33 PM, Bruno Grande wrote:
I was looking for a way of typecasting attributes that are mapped to
Integer
On 5/14/15 12:43 PM, Jonathon Nelson wrote:
And indeed you are correct. However, this comes as quite a surprise to me.
As an idiom:
try:
do_stuff()
except SomeError, e:
make_some_noise(e)
maybe_return_here_etc
is a pretty common idiom. I tried deleting 'e' within the except
The code is here:
https://github.com/rbuck/sqlalchemy-nuodb
Instructions (notably for pip dependencies) are documented in the
README.rst file.
The test is the SQL Alchemy compliance test suite. I am down to 12 or less
failures now, so I am almost defect free.
On 5/14/15 8:02 AM, Robert Buck wrote:
I am authoring a dialect for our database technology and one of the
tests is failing, but I am not quite sure why, or how to proceed.
Would someone know where I'd look, or what I may be missing, to fix
this aspect of the dialect?
I am likely missing
Can you share the test and any relevant code (ie, anything in the dialect
that deals with this)?
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
