-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Returning as dict #47
Comments
What do you mean? Could you give an example of what you would like and how it looks now? |
+1 on @ToffeeCrunch's suggestion. We can probably have a constructor argument where you pass in a class that overrides getattr, is that what you mean? |
This would also be nice to support indexing the columns in order (with a different kind of class, of course). Right now AFAIK it's not possible to know what the original key order is. |
@sbirch that would be possible by returning OrderedDicts instead of dicts.. Actually a good idea I think. |
OrderedDict support added in branch ordered-dicts |
Woohoo! That will be very useful to me. Though I still think there's value in @JosephShering's original suggestion, as it provides the flexibility to do things like what you did without forking it. (Attribute accessors would be very nice too, for example.) |
FYI: right now SQLAlchemy's |
It's |
I would really like it if object were returned instead of dictionaries, it would make looping over the results a lot easier
The text was updated successfully, but these errors were encountered: