Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dealing with non-tuple cursors *or* introducing a row factory #3

Closed
kgaughan opened this issue Apr 16, 2012 · 1 comment
Closed

Dealing with non-tuple cursors *or* introducing a row factory #3

kgaughan opened this issue Apr 16, 2012 · 1 comment

Comments

@kgaughan
Copy link
Owner

The former depends on only on being able to tell if the row is a tuple, with the assumption otherwise being that it's a dict-like object. The may break, however, and will likely be slower than I'd like.

Alternatively, some kind of row factory can be implemented. This would be akin to the way the sqlite3 driver for Python works. This has the advantage of keeping the likes to query_value and query_column fast, but it may slow down query() and query_row().

I'm strongly leading towards the latter.

@kgaughan
Copy link
Owner Author

Done! Went down the row factory route.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant