zzzeek / sqlalchemy_old / issues / #1607 - MaxDB dialect broken since Row/ResultProxy refactor — Bitbucket

Issue #1607 resolved

Former user created an issue 2009-11-06

(original reporter: ged) MaxDBCachedColumnRow uses _get_col which doesn't exist anymore

Comments (5)

Mike Bayer repo owner
you've been running the tests on maxdb ? i haven't updated the maxdb dialect for 0.6 at all.
- 2009-11-06T10:13:16+00:00
Mike Bayer repo owner
- assigned issue to
- changed milestone to 0.6.xx
- 2009-11-15T11:46:48+00:00
Former user Account Deleted
(original author: ged) Replying to zzzeek:

you've been running the tests on maxdb ? i haven't updated the maxdb dialect for 0.6 at all.

No, I haven't. I just noticed it still used _get_col, which cannot work. I guess the summary should have been "even more broken".
- 2009-11-15T12:52:29+00:00
Mike Bayer repo owner
- changed milestone to blue sky
- 2011-11-16T00:53:26+00:00
Mike Bayer repo owner
- changed status to wontfix
maxdb is moved out to https://bitbucket.org/zzzeek/sqlalchemy-maxdb, so any interest in fixing maxdb can be over there.
- 2012-11-24T19:58:06+00:00
Log in to comment

Assignee: –

Type: bug

Priority: major

Status: resolved

Component: –

Milestone: blue sky

Votes: 0

Watchers: 0

Jira: the preferred issue tracker for Bitbucket. Join the team!