You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
It would be a nice low-level assist from the DBAPI to SELECT fields from the DB and, before returning the result, convert(TargetType, field)ing the field values to the types the queryor will use.
The text was updated successfully, but these errors were encountered:
Yes, I have been thinking about a version of fetchinto_ that takes a container type and constructs and returns that container. I think that would satisfy this?
Thanks for contributing :) feel free to open any other feature request or idea issues, as I want to take many perspectives into account with this package.
Python DBI2 is not all that compelling -- it is a least likely to offend, erstwhile attempt at genericity.
Times have changed some. I have no qualm with using it to make sure 'bases are covered'.
What is your opinion of SQLAlchemy (not that that should be the DBI -- that the DBI should allow such constructions (the Julia way) to become available with more ease and less expertise.
It would be a nice low-level assist from the DBAPI to SELECT fields from the DB and, before returning the result, convert(TargetType, field)ing the field values to the types the queryor will use.
The text was updated successfully, but these errors were encountered: